BBOUT extremely large on bb16e1

Hi

    Thanks for your advice. I think I shall back up the file
and stop bb 
from running before clearing it.
However, is there a way to check if any process is indeed
writing to the 
inode in the situation that you
mentioned, and if so, is there a way to salvage it?

regards

----- Original Message ----- 
From: "Strandell, Ralf" <Ralf.Strandellsilja.com>
To: <bbbb4.com>
Sent: Wednesday, March 22, 2006 11:48 PM
Subject: RE:  BBOUT extremely large on bb16e1


> Hi,
>
> BBOUT is basically an error file. How about removing
the errors that
> cause the messages?
> What kind of messages do you see in BBOUT?
>
> A "/bin/mv /home/bb/BBOUT
/home/bb/BBOUT.old" in crontab is better than
> "cat /dev/null > BBOUT".
> You will then allways have some error messages left, in
case you would
> need them.
> You could start by moving the file once a month.
>
> If you move the file at the same time that some process
has it opened
> for writing, then "fun things" might
happen: The process continues to
> write to the same inode (disk area) that now has the
name BBOUT.old. If,
> on the other hand, you choose to "rm BBOUT"
then the file name is
> removed from the directory structure, but if some
process has the file
> (inode) open for writing during that rm, you will end
up in a situation
> where the file is not visible anywhere, but the process
is unaware of
> that and continues to write to the inode. This ghost
file consumes disk
> space and continues to grow as usual... I'm sure that
any trouble will
> be gone by next reboot, though. This happens on the
vxfs file system.
> Might also be true in other file systems, so beware.
Having some process
> write data to disk without creating a visible file
feels real bad
> (especially if you are the sysadmin). So avoid deleting
files that are
> opened for writing. Moving is safer. Shutting down bb
(and ALL its child
> processes) prior to working with BBOUT is even more
safe.
>
> -----Original Message-----
> From: owner-bbbb4.com [mailto:owner-bbbb4.com]
On Behalf Of Joshua Au
> Sent: Thursday, March 23, 2006 9:57 PM
> To: bbbb4.com
> Subject:  BBOUT extremely large on bb16e1
>
> Hi,
>
>    I noticed that even for the clients that bb is
monitoring, the BBOUT
> in
> bb/bb16e1 is extremely large. Is it advisable to cat
/dev/null > BBOUT
> the file or is there some other way to minimise the
hard disk usage of
> BB as the partition that bb is installed on is rather
small.
>
> regards, Josh
>
>
> --
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=
-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the
bb-digest list
> send e-mail to mailto:majordomobb4.com with unsubscribe bb
-and/or-
> subscribe bb-digest in the BODY of the message.
>
> --
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=
-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the
bb-digest list
> send e-mail to mailto:majordomobb4.com with unsubscribe bb
-and/or-
> subscribe bb-digest in the BODY of the message.
> 


--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=
-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the
bb-digest list
send e-mail to mailto:majordomobb4.com with unsubscribe bb
-and/or-
subscribe bb-digest in the BODY of the message.