xfs-masters
[Top] [All Lists]

[xfs-masters] Re: potential xfs_repair bug

To: xfs-masters@xxxxxxxxxxx
Subject: [xfs-masters] Re: potential xfs_repair bug
From: Steve Lord <lord@xxxxxxx>
Date: Thu, 02 Sep 2004 16:15:59 -0500
Cc: Eric Sandeen <sandeen@xxxxxxx>, Junfeng Yang <yjf@xxxxxxxxxxxx>
In-reply-to: <Pine.GSO.4.44.0409021340120.15188-100000@xxxxxxxxxxxxxxxxxxxxx>
References: <Pine.GSO.4.44.0409021340120.15188-100000@xxxxxxxxxxxxxxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.7.1 (X11/20040626)
Junfeng Yang wrote:
> 
>>>I suspect what you are doing with this change is making repair fail
>>>in the middle of creating the lost+found dir, repair always does that.
>>>
> 
> 
> Hi Steve,
> 
> you mean xfs_repair creates lost+found everytime it runs?  I'm not sure if
> the crash happens in the middling of creating lost+found, as our checker
> only sees block writes with little file system knowledge.  We caught this
> warning automatically (w/o chaing the xfs_repair code).
> 
> so is it true that in the rare case that xfs_repair fails in the middle of
> creating lost+found, '/.' can be wiped off?  do you guys consider this as
> a bug?

Well, I don't work on xfs anymore really, I just watch from the sidelines.
It is a pretty small window in reality, but it probably says that while
repair is running the filesystem is vulnerable to machine outages.

Getting repair out of that hole would be a big job I suspect. It would
need to implement a journal and do all its work that way. Hmm, I cannot
remember if it actually does that for the most part to be honest.

Steve


<Prev in Thread] Current Thread [Next in Thread>