From owner-freebsd-questions Fri Mar 24 9:41:39 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4BBF437B67F for ; Fri, 24 Mar 2000 09:41:36 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e2OI5IA22070; Fri, 24 Mar 2000 10:05:18 -0800 (PST) Date: Fri, 24 Mar 2000 10:05:18 -0800 From: Alfred Perlstein To: Troy Settle Cc: freebsd-questions@FreeBSD.ORG Subject: Re: filesystem full? Message-ID: <20000324100518.O21029@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from troy@picus.com on Fri, Mar 24, 2000 at 06:55:18AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Troy Settle [000324 04:24] wrote: > > Hey all, > > I've seen this come up before, but don't remember seeing an answer. > > After some 200 days of uptime, one of my boxes decided to play stupid and > pretend like the /var filesystem was full. As you can imagine, this screwed > up all sorts of things. Not until I did a reboot, did the machine start > behaving properly. > > > Now, as you can see with the information below, du doesn't show a difference > of the before and after, yet df does. > > This problem, whatever it is, is a serious threat to FreeBSD's claim of > stability. 200 days is a good, long time, and this machine is due for an > update anyways, but I would have expected that it could have stays up > indefinately. This box has been rock solid until it started loosing it's > marbles. It's more likely that some program or person has a large file open in /var that has been deleted, the space on the disk can't be freed until the program closes the file or exits. So the next time you see this, try stopping and restarting several daemons before making silly claims about stability issues. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message