From owner-freebsd-current@FreeBSD.ORG Thu Mar 12 17:37:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E131E1065689 for ; Thu, 12 Mar 2009 17:37:14 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id B19288FC22 for ; Thu, 12 Mar 2009 17:37:14 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LhoqH-0004dH-MW for freebsd-current@freebsd.org; Thu, 12 Mar 2009 10:37:13 -0700 Message-ID: <22481640.post@talk.nabble.com> Date: Thu, 12 Mar 2009 10:37:13 -0700 (PDT) From: Jakub Lach To: freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jakub_lach@mailplus.pl References: Subject: Re: Filesystems being eaten? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 17:37:16 -0000 Christian Weisgerber wrote: > > Last Friday my 8.0-CURRENT/amd64 box suffered a crash--no idea if > it panicked, I was running X11--after which all filesystems were > so badly corrupted that I had to reinstall the machine. This was > a vanilla setup, UFS2 and UFS2+S, -CURRENT about a week old at the > time. > > Yesterday it crashed again and while other filesystems survived, > /usr was again too damaged for fsck to recover it. fsck -y showed > thousands of errors in the "unexpected soft update inconsistency" > class, starting with many "partially allocated inode"s, and eventually > asked to be re-run, which produced only more of the same. I wonder > if fsck didn't cause most of the corruption itself. > > I realize this isn't exactly helpful as a bug report, but what can > I do. Something in -CURRENT from the last two weeks or so, maybe > specific to amd64, maybe not, may eat filesystems. > > Since I actually use the box and can't afford to reinstall it once > or twice a week, I've moved it to RELENG_7 for the time being. > > -- > Christian "naddy" Weisgerber naddy@mips.inka.de > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > I had similar problem with /usr, after fsck re-run cleaning and reconnecting suddenly it bootted. -- View this message in context: http://www.nabble.com/Filesystems-being-eaten--tp22478626p22481640.html Sent from the freebsd-current mailing list archive at Nabble.com.