Re: How a full fsck screwed up my SU+J filesystem

From: Michael Butler <imb_at_protected-networks.net>
Date: Thu, 02 Dec 2010 09:03:34 -0500
On 12/01/10 19:30, Kirk McKusick wrote:

 [ .. snip .. ]

> 
> Thanks all: Garrett for the report, Peter for the way to reproduce
> the problem, and Kostik for a fix. I have copied Jeff so that he can
> confirm that Kostik's fix is the appropriate thing to do. And I will
> take a look at fsck to see if I can make it a bit more paranoid about
> removing .sujournal.
> 
> 	Kirk McKusick

There's another case that SU+J fails and the patch has not yet been
committed .. specifically, when configure tries to do a directory rename
test .. as below ..

I am uncertain but it seems that 'dump -L' exhibits a similar behaviour
.. completely hung on me at 1am this morning :-(

	imb

-------- Original Message --------
Subject: Re: softupdate with journal panic
Date: Tue, 24 Aug 2010 00:12:57 +0300
From: Kostik Belousov <kostikbel_at_gmail.com>
To: Peter Holm <pho_at_freebsd.org>
CC: Michael Butler <imb_at_protected-networks.net>,        Jeff Roberson
<jroberson_at_jroberson.net>, current_at_freebsd.org

On Sun, Aug 22, 2010 at 03:21:04PM +0200, Peter Holm wrote:
> On Sat, Aug 21, 2010 at 01:49:45PM -0400, Michael Butler wrote:
> > While updating sysutils/coreutils port on -current as of this morning
> > (SVN r211550), I noted a panic during the directory rename config test.
> >
>
> Your problem seems identical to this report:
>
>
http://docs.freebsd.org/cgi/mid.cgi?AANLkTinPjiOV21kDLZYV5WScrhLMN7DY8E8jVHWPU5mC
>
I believe that dotdotremref in this case is legitimately NULL. With this
assumption, the following patch would help.


Received on Thu Dec 02 2010 - 13:03:42 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:09 UTC