Date: Thu, 12 Mar 2009 10:37:13 -0700 (PDT) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-current@freebsd.org Subject: Re: Filesystems being eaten? Message-ID: <22481640.post@talk.nabble.com> In-Reply-To: <gpb71c$ni9$1@lorvorc.mips.inka.de> References: <gpb71c$ni9$1@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22481640.post>