Date: Sun, 26 Jul 2015 18:34:02 -0400 From: Michael Sierchio <kudzu@tenebras.com> To: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: Endless Data Loss Message-ID: <CAHu1Y72Ng=OpC6BqNXdYwveRt2RjFZX86X0CZwTEYdsgnPcDgQ@mail.gmail.com> In-Reply-To: <20150726210150.GG1843@mordor.lan> References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> <CAFYkXjknSK=%2BnpPg67vpLwtYJRRdHFmX=Jxp%2BCGGZcTHq3%2BGxQ@mail.gmail.com> <20150726210150.GG1843@mordor.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 26, 2015 at 5:01 PM, Julien Cigar <jcigar@ulb.ac.be> wrote: On Sat, Jul 25, 2015 at 06:30:38PM +0200, CeDeROM wrote: > > > UFS2 SU+J has failed me several times as well. I also ocassionaly > > experienced root filesystem corruption that prevented valid boot. Even > on a > > fresh install and new hardware I consider UFS2 SU+J unreliable.. I am not > > sure why this got into production :-( > > Same here.. (on 10.1-RELEASE) > > I turned off soft updates journaling on all my machines since the day > one of my file system (on a production machine) was corrupted. This has been my experience as well. SU+J also breaks filesystem snapshots, which are incredibly useful for dump, tarsnap, etc. - M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y72Ng=OpC6BqNXdYwveRt2RjFZX86X0CZwTEYdsgnPcDgQ>