Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Mar 2012 17:57:15 -0300
From:      H <hm@hm.net.br>
To:        David Thiel <lx@freebsd.org>
Cc:        Adrian Chadd <adrian@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: Heavy fs corruption with 9.0-RELEASE
Message-ID:  <4F5E632B.1060305@hm.net.br>
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
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFDA339C6775EFA629C94DBDB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

David Thiel wrote:
> On Fri, Mar 09, 2012 at 01:53:59AM -0800, Adrian Chadd wrote:
>> PR ?
> The original thread was here:
>
> http://marc.info/?t=3D132502460000001&r=3D1&w=3D2
>
> Ignore the part where it takes me a while to figure out fsck isn't=20
> 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=20
> 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=20
> then regular fsck, both using the -v flag (with output piped to some=20
> other fs)? Can you also see if:

have you ever thought about that the real problem could be that fsck can
not determine the fs type soon the partition is dirty?

in my experience it does not matter if it is SU or SUJ, the problem is
that fsck bails out and the system boots normally even with bad blocks,
because of this fatality the errors are dragged from boot to boot and
things are getting worse

since I added -t ufs to /etc/rc.d/fsck I have no problems anymore with
this issue

background fsck of course must be disabled and fsck_yes enabled

H





> kern.cam.ada.write_cache=3D0
> hw.ata.wc=3D0
>
> 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 ou=
t.
>>>> All the system were installed through the standard installation
>>>> procedure. After unclean reboot, either crash or power-failure, I ge=
t
>>>> 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 disappea=
r.
>>>
>>> _______________________________________________
>>> 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.or=
g"


--=20
H
+55 11 4249.2222



--------------enigFDA339C6775EFA629C94DBDB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9eYzAACgkQvKVfg5xjCDwkxwCeJvat+MpJDiPAwrgrCJZaYxAN
zjwAnibtT/9x1oG7YcCxGm0kQd2BePua
=kSIW
-----END PGP SIGNATURE-----

--------------enigFDA339C6775EFA629C94DBDB--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5E632B.1060305>