From owner-freebsd-questions Sat Nov 16 11:10:13 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87F1637B401 for ; Sat, 16 Nov 2002 11:10:12 -0800 (PST) Received: from csts1.csts.org (12-229-161-203.client.attbi.com [12.229.161.203]) by mx1.FreeBSD.org (Postfix) with SMTP id A77A443E4A for ; Sat, 16 Nov 2002 11:10:11 -0800 (PST) (envelope-from calvins@csts.org) Received: (qmail 16743 invoked from network); 16 Nov 2002 19:14:33 -0000 Received: from unknown (HELO ces) (192.168.1.151) by 0 with SMTP; 16 Nov 2002 19:14:33 -0000 Message-ID: <010601c28da3$fb7aa620$9701a8c0@home> From: "Calvin Smith" To: References: Subject: Re: A quizical Date: Sat, 16 Nov 2002 11:11:35 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > /dev/ad0s1e 99183 99068 -7819 109% /var [...] > > Showing /var at 109% capacity, over 99 megs. [...] > > The thing is this ... du feels differently ... [...] > > Little over a meg ... not nearly 100. So the question becomes > > where's the beef? > > It's possible that some running process has unlinked a file on the /var file > system but still has it open. On UNIX, you can unlink (delete) a file while > it's open to keep it from appearing in the 'ls' and 'du' output, but 'df' > will see the space used. If that's the case here, then when the file is > closed the space will be recovered. I'm not sure what utilities are > available to show which processes have space allocated (I'd sure like to > know of one, though) but if you kill the offending process then the unlinked > file space will be recovered. Easiest solution would be to reboot the > machine, but you would still need to discover the cause or it will happen > again. > > On the other hand, you might have a different problem. IDK. > > Paul There is a pretty good discussion of a very similar problem, this can be found at http://www.spinics.net/lists/ext3/ and find the reference "100% full". Calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message