xfs
[Top] [All Lists]

Re: "No such file or directory" (still) (was Re: file corruption during

To: "Steve Lord" <lord@xxxxxxx>
Subject: Re: "No such file or directory" (still) (was Re: file corruption during emacs build on XFS logical volume
From: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Date: Tue, 08 Jan 2002 18:15:47 +0100
Cc: "Linux XFS" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1010508821.25799.12.camel@jen.americas.sgi.com>
Reply-to: "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Tue, 08 Jan 2002 10:53:41 -0600, Steve Lord wrote:

[...]
>So all of these are single byte errors in the directory names. From the

Right.

>case we looking into detail on we saw that the name was correct at one
>point in the code - we managed to create the correct hash, but the
>directory name block has a single byte error. Once names are layed
>down into the directory block we never touch them, so there is very
>little code which has a chance to mess with the bytes.

Hmmmm. I don't like what you're suggesting... :-(

You think the problem might be within the RAID firmware?

>Is is possible to turn your raid into a jbod and do this on software
>raid instead - I do not think the config is important. I want to see
>if the error is going to change if we take the hardware raid out of
>the system.

No, I can't reconfigure it as a JBOD. :-(

Do you happen to know some sort of tool that might be able to do this kind of 
"integrity checks?" Or any other idea what I could do to make sure it isn't 
the RAID that's causing the problems?


-- 
Verkaufe Original-BMW-Raeder:                    L I N U X       .~.
http://adsl-bergs.rz.rwth-aachen.de/~rabe       The  Choice      /V\
                                                 of a  GNU      /( )\
                                                Generation      ^^-^^



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