From owner-freebsd-stable@FreeBSD.ORG Wed Apr 2 08:17:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E669D1065681 for ; Wed, 2 Apr 2008 08:17:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id D5EF78FC31 for ; Wed, 2 Apr 2008 08:17:17 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 9C6451CC060; Wed, 2 Apr 2008 01:17:17 -0700 (PDT) Date: Wed, 2 Apr 2008 01:17:17 -0700 From: Jeremy Chadwick To: Ingeborg Hellemo Message-ID: <20080402081717.GA40810@eos.sc1.parodius.com> References: <200804020812.m328CUeh029574@barnetv.cc.uit.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200804020812.m328CUeh029574@barnetv.cc.uit.no> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Volodymyr Kostyrko , freebsd-stable@freebsd.org Subject: Re: /var with capacity -1% X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2008 08:17:18 -0000 On Wed, Apr 02, 2008 at 10:12:30AM +0200, Ingeborg Hellemo wrote: > ~/#fsck /dev/da0s1d > ** /dev/da0s1d (NO WRITE) > ** Last Mounted on /var > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? no > > 275 files, 7699 used, 2549244 free (596 frags, 318581 blocks, 0.0% > fragmentation) > > After reboot to single mode and fsck -y we are back to a more normal state: > > ~/>df /var > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1d 5077038 14448 4656428 0% /var > > But shouldn't I have been notified of this error during previous reboots? Did you have any recent crashes, panics, or anything that could (even remotely) cause filesystem inconsistencies? If not, then the best explanation is then bit rot, or bad hardware causing corruption of data. Jeff Bonwick wrote a blog entry about this kind of problem: http://blogs.sun.com/bonwick/entry/zfs_end_to_end_data I suppose there could be a bug in FFS, but I would expect a significantly larger number of users to be reporting this... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |