Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Dec 2005 10:35:00 -0600
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Colin Farley <Colin.Farley@ecarecenters.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: free space reported incorrectly
Message-ID:  <20051214163500.GA18296@dan.emsphone.com>
In-Reply-To: <OF3F4C3057.10C651D9-ON862570D7.00522CC6-862570D7.00543398@ecarecenters.com>
References:  <OF3F4C3057.10C651D9-ON862570D7.00522CC6-862570D7.00543398@ecarecenters.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 14), Colin Farley said:
> I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail
> relays/web servers.  Today I noticed that one had a lot more space in
> /var used.  I figured that a log was growing and started to
> investigate.  After running du -h /var and seeing it come up with a
> total usage much less than what df -h reports I decided to run fsck
> /var.  This is the output I get:
> 
> ** /dev/da1s1f (NO WRITE)

Don't trust any fsck output on a mounted filessytem.

You probably have some logfiles that got manually rotated or deleted
(i.e. not via newsyslog), and syslogd was never told to close&reopen
the logfile.  Run "lsof +L1" (lsof is in ports) to find the offending
processes and restart them.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051214163500.GA18296>