Date: Wed, 14 Dec 2005 16:01:07 -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: <20051214220107.GB18296@dan.emsphone.com> In-Reply-To: <OF6BED90E6.19DFB737-ON862570D7.0077170E-862570D7.0078076F@ecarecenters.com> References: <20051214163500.GA18296@dan.emsphone.com> <OF6BED90E6.19DFB737-ON862570D7.0077170E-862570D7.0078076F@ecarecenters.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 14), Colin Farley said: > Thanks for the reply. I have found as suspected that apache is > responsible. Since these servers are redundant using UCARP I am > planning to shut down the services, unmount /var and run fsck, one at > a time. I'm just not sure why I cannot see these files but hopefully > fsck will make them visable or just remove them for me. I think at > the same time I will make a change to my apache log rotation strategy > as it appears to be causing the problems. You can't see the files because they have been deleted. As long as a process holds a filehandle open on the file, however, the file still exists and consumes space in the filessytem. Killing the apache processes (or sending this the appropriate "reopen your logfiles" signal) will suffice to free the space up. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051214220107.GB18296>