Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Mar 2011 21:33:05 -1000 (HST)
From:      Jeff Roberson <jroberson@jroberson.net>
To:        Doug Barton <dougb@FreeBSD.org>
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>, Marius Strobl <marius@alchemy.franken.de>, svn-src-head@freebsd.org, svn-src-all@freebsd.org
Subject:   Re: svn commit: r219667 - head/usr.sbin/bsdinstall/partedit
Message-ID:  <alpine.BSF.2.00.1103202130200.1480@desktop>
In-Reply-To: <4D8662B0.8000705@FreeBSD.org>
References:  <4D840BD0.4030306@freebsd.org> <201103200000.p2K00pue003373@chez.mckusick.com> <20110320162212.GI1606@alchemy.franken.de> <4D8662B0.8000705@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Mar 2011, Doug Barton wrote:

> 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.
>

So you're saying the directory entry was missing?  Can you tell me how big 
the directory was?  Number of files?  Approximate directory size when you 
consider file names?  When you fsck'd were inodes recovered and linked 
into lost and found?  What was the actual path?

I'm trying to wrap my head around how this would be possible and where the 
error could be and whether it could be caused by SUJ.  The number of 
interactions with disk writes are minimal.  Corruption if it occurs would 
most likely be caused by a bad journal recovery.

Thanks,
Jeff

> 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?alpine.BSF.2.00.1103202130200.1480>