Rusty,
;) that's just it...I didn't delete anything and that's why I was
wondering why there was such a difference in the readings I was getting
from these two programs.
--
Mark
*****
"what knowledge I have managed to accumlate over the years
at times becomes obscured and even hidden amidst the vast
emotional onslaught of my children. You never finish being a parent. :)"
On Tue, 15 May 2001, Rusty Carruth wrote:
> Mark Weaver <[EMAIL PROTECTED]> wrote:
> > Hi list,
> >
> > I've got a problem here that isn't making any sense to me. This morning
> > one of the leg messages reported that there wasn't any more space left on
> > /var. that's ok cause it wasn't any big deal to fix that. what I did have
> > a problem with is the difference free space that is being reported by two
> > different programs on the system.
> >
> > df reports it this way:
> >
> > [mdw1982@mdw1982 mdw1982]$ df -h
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/hdc6 787M 757M 30M 96% /var <-- the critical reading
> > ---------------------------------------------------------
> > ...and du reports it this way:
> >
> > 469M /var <-- the critical reading
> > ...
>
> Someone suggested the blocking factor as the cause for this.
>
> I doubt that your block size is big enough for the effect you are
> seeing. I'd guess that some program has a file open on /var, but
> the file has been deleted from the directory.
>
> Until the program exits, the space is UNAvailable, but not
> *visible* to any program other than the one that has it open.
>
> So, what 288 meg file did you delete that some program still has
> open? (Maybe a log file? Probably not a core file ;-)
>
> rc
>
>
> Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
> Voice: (480) 345-3621 SnailMail: Schlumberger ATE
> FAX: (480) 345-8793 7855 S. River Parkway, Suite 116
> Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
> ICBM: 33 20' 44"N 111 53' 47"W
>
