From owner-freebsd-questions Wed Sep 8 4:25:39 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mailhost.criterion.canon.co.uk (mailhost.criterion.canon.co.uk [194.223.249.254]) by hub.freebsd.org (Postfix) with ESMTP id 9666114F05 for ; Wed, 8 Sep 1999 04:25:35 -0700 (PDT) (envelope-from adamn@csl.com) Received: from csl.com (hermes.criterion.canon.co.uk [194.223.249.13]) by mailhost.criterion.canon.co.uk (8.8.8/8.7.3) with ESMTP id MAA00146; Wed, 8 Sep 1999 12:13:06 +0100 (BST) Message-ID: <37D6471C.ACABF478@csl.com> Date: Wed, 08 Sep 1999 12:23:08 +0100 From: Adam Nealis Organization: Criterion Software, Ltd. X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.34 i686) X-Accept-Language: en MIME-Version: 1.0 To: Ben Williams Cc: Jonathan Chen , FreeBSD questions Subject: Re: /var slice wierdness References: <2148.990908@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Williams wrote: > > Jonathan, > > Thank you VERY much for the info. I tried HUP'ing all my daemons to > get whoever was holding a now-non-existent fd open to release it but > that didn't work so I bounced the server and when it came back up my > df reported that I had less than 20% used in /var. A less drastic method might be to use lsof on /var (see /usr/ports/sysutils/lsof - it can be used to report files open per process, processes with open files per volume or per directory and much more. /usr/local/sbin/lsof /tmp COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME imapd 1969 adamn 5uW VREG 0,131076 4 77 /tmp (/dev/wd0s1e) imapd 2017 adamn 5uW VREG 0,131076 4 80 /tmp (/dev/wd0s1e) imapd 2025 adamn 5uW VREG 0,131076 4 81 /tmp (/dev/wd0s1e) imapd 2054 adamn 5uW VREG 0,131076 4 82 /tmp (/dev/wd0s1e) > > TAF > -- > Ben > > On or about Tuesday, September 07, 1999, sometime around 6:11:22 PM, you said: > JC> On Tue, 7 Sep 1999, Ben Williams wrote: > > >> I also have another box (a server) that is having some serious > >> wierdness in the /var slice. This was only my second FreeBSD install > >> and I went with the defaults for slice sizes which has been fine up > >> until about a week ago when I noticed /var was nearly full, but a `du -x | sort -n` doesn't show me anything hoggging all my space > >> up. Here is what I have: > > JC> It's very likely that there's a process holding a file open on /var > JC> that doesn't appear on the directory listings. (ie process opens > JC> a file on /var/tmp, then unlinks it). Only when the process dies > JC> does the filespace it consumes get released. > > JC> Jonathan Chen > JC> ------------------------------------------------------------------------ > JC> "We laugh in the face of danger, we drop icecubes down the vest of fear" > JC> - Edmond Blackadder III > > JC> To Unsubscribe: send mail to majordomo@FreeBSD.org > JC> with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message