Disc Free (df) weirdness (FC2)

[Mike McCarty]

Peter Arremann wrote:
> On Friday 07 October 2005 15:01, Mike McCarty wrote:
> 
>>But what is there which would do that with about 1G of disc
>>that I didn't intentionally run? To put it another way, what
>>"application" is there that would have such a file both deleted
>>and held open, but which would not be stopped when I had closed
>>all windows, then opened just one xterm (or I guess gnome-terminal)
>>for command-line use?
> 
> Why are you so fixed that it has to be an "application" that you started?

I'm not. I keep getting messages stating that "applications" do so-
and-so and I'm asking what app would do that which wouldn't
be stopped by being closed. The question is not quite, but almost,
rhetorical.

Even so, what system process eats about a GIG of disc, and deletes it,
but holds it open (or another process holds it open)?

> Just booting a system will start dozens of processes that can show issues.

Please tell me which process started during boot eats about 1G
of disc, which it then deletes, but still has open so that the resources
are not freed? In any case, no reboots were done in the intervening
period, except that which freed up the disc.

> In the past, i've seen issues with mysql, nfs, dhcpclient, cupsd and apache 
> that all caused the problem you described. Usually it turns out though that  

I don't run any of those but cups and nfs. I haven't done an nfs mount
since last, umm, January, and there have been quite a few reboots since
then.

$ ps -A | grep sql
$ ps -A | grep nfs
$ ps -A | grep dhcp
$ ps -A | grep cups
  3610 ?        00:00:00 cupsd
  4480 ?        00:00:03 eggcups
$ ps -A | grep apache
$

No big print jobs, no print jobs at all, run in the intervening
interval.

> the user simply forgot to restart a process after removing one of its files 
> by hand. 

I haven't done that, either. And nobody has logged onto this machine but
me.

> But I guess we will never find out. By rebooting the system you have taken 
> away any chance of finding the root cause of your issue. Next time you get 
> into a situation like that, use the lsof command to check and then you will 
> see what's going on. 

Thanks, I'll certainly do that.

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!