From owner-freebsd-bugs@FreeBSD.ORG Fri Jan 27 21:50:08 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CA1116A420 for ; Fri, 27 Jan 2006 21:50:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 611D943D46 for ; Fri, 27 Jan 2006 21:50:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0RLo7Kt043615 for ; Fri, 27 Jan 2006 21:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0RLo7Tg043614; Fri, 27 Jan 2006 21:50:07 GMT (envelope-from gnats) Date: Fri, 27 Jan 2006 21:50:07 GMT Message-Id: <200601272150.k0RLo7Tg043614@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jean-Sebastien Roy Cc: Subject: Re: kern/92432: negative used disk space X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jean-Sebastien Roy List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 21:50:08 -0000 The following reply was made to PR kern/92432; it has been noted by GNATS. From: Jean-Sebastien Roy To: Kris Kennaway Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/92432: negative used disk space Date: Fri, 27 Jan 2006 22:43:07 +0100 Kris Kennaway wrote: >> While I understand "available" space could be negative, a negative >> "used" space is quite strange. > > This seems to be due to FS corruption. umount the filesystem and > fsck -f it. fsck -f fixes it, thanks. It seemed to be fixed by each reboot and still kept coming back so I never tried to force fsck. I never had any error message about it while booting or in /var/log/messages. Assuming "fsck -f" fixes it definitely, when such problems occur, should a message be output and the file system be marked "unclean" or something like that so that a reboot would somehow force the user to "fsck -f" ? (sorry if if seems stupid). Thanks again, Regards, js