Date: Fri, 9 Mar 2012 13:53:17 -0800 From: Adrian Chadd <adrian@freebsd.org> To: David Thiel <lx@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Heavy fs corruption with 9.0-RELEASE Message-ID: <CAJ-Vmo=yacJg62Yvt4njAOEBjAnrxW3zc5XYauq4yZsTGJ1dyQ@mail.gmail.com> In-Reply-To: <20120309200244.GL88589@redundancy.redundancy.org> References: <CACqU3MW734kWjNxH2SWHBb_ERiN9TE0ju6DM%2BAh8zkGmh-j5TA@mail.gmail.com> <20120308190713.GH88589@redundancy.redundancy.org> <CAJ-Vmo=3G%2Bcg9u1vam7_DJu4RiNuYG_FnfcjGVo2ypQLjNh0FQ@mail.gmail.com> <20120309200244.GL88589@redundancy.redundancy.org>
next in thread | previous in thread | raw e-mail | index | archive | help
You didn't answer my question - is there a PR opened for this? Adrian On 9 March 2012 12:02, David Thiel <lx@freebsd.org> wrote: > On Fri, Mar 09, 2012 at 01:53:59AM -0800, Adrian Chadd wrote: >> PR ? > > The original thread was here: > > http://marc.info/?t=132502460000001&r=1&w=2 > > Ignore the part where it takes me a while to figure out fsck isn't > softupdate-aware. > > There was further followup off-list with the associated SUJ developers > with clearer test results, but no definitive resolution as of yet, as > far as I know. I didn't get a chance to test the write cache disabling > approach or do further testing before I had to turn off SUJ. > > Arnaud: Would you be able to record a few test cases with SUJfsck and > then regular fsck, both using the -v flag (with output piped to some > other fs)? Can you also see if: > > kern.cam.ada.write_cache=0 > hw.ata.wc=0 > > while leaving SUJ enabled helps at all? > >> On 8 March 2012 11:07, David Thiel <lx@freebsd.org> wrote: >> > On Mon, Mar 05, 2012 at 05:12:16PM -0500, Arnaud Lacombe wrote: >> >> I've been running a couple of system with 9.0-RELEASE since it is out. >> >> All the system were installed through the standard installation >> >> procedure. After unclean reboot, either crash or power-failure, I get >> >> a huge amount of really bad filesystem corruption (read: "silent", >> >> fs-wide, corruptions). This happens with either i386 or amd64 build. >> >> Systems involved use compact flash as their system permanent storage >> >> medium. >> > >> > I have had this same behavior on every SUJ system I've built, both on >> > SSDs and otherwise, on i386, PPC and amd64. Remove SUJ and revert to >> > plain softupdates, and I strongly suspect your problems will disappear. >> > >> > _______________________________________________ >> > freebsd-stable@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=yacJg62Yvt4njAOEBjAnrxW3zc5XYauq4yZsTGJ1dyQ>