Date: Sun, 20 Mar 2011 13:25:20 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Marius Strobl <marius@alchemy.franken.de> Cc: src-committers@freebsd.org, kvedulv@kvedulv.de, Jeff Roberson <jeff@freebsd.org>, Kirk McKusick <mckusick@mckusick.com>, Gavin Atkinson <gavin@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, svn-src-head@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r219667 - head/usr.sbin/bsdinstall/partedit Message-ID: <4D8662B0.8000705@FreeBSD.org> In-Reply-To: <20110320162212.GI1606@alchemy.franken.de> References: <4D840BD0.4030306@freebsd.org> <201103200000.p2K00pue003373@chez.mckusick.com> <20110320162212.GI1606@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/20/2011 09:22, Marius Strobl wrote: > I fear it's still a bit premature for enable SU+J by default. Rather > recently I was told about a SU+J filesystems lost after a panic > that happend after snapshotting it (report CC'ed, maybe he can > provide some more details) and I'm pretty sure I've seen the problem > described in PR 149022 also after the potential fix mentioned in its > feedback. +1 I tried enabling SU+J on my /var (after backing up of course) and after a panic random files were missing entirely. Not the last updates to those files, the whole file, and many of them had not been written to in days/weeks/months. With all due respect to the hard work that went into the code, I would be very uncomfortable with enabling it by default at this point. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8662B0.8000705>