xfs
[Top] [All Lists]

Re: Are these errors bad? xfs_repair finding errors.

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: Are these errors bad? xfs_repair finding errors.
From: Quentin Arce <qarce@xxxxxxxxx>
Date: 15 May 2002 11:29:51 -0700
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20020514094608.P120284@wobbly.melbourne.sgi.com>
References: <1021134063.3827.978.camel@qarce-lnx> <20020514094608.P120284@wobbly.melbourne.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
Thank YOU!!!

Q


On Mon, 2002-05-13 at 16:46, Nathan Scott wrote:
> On Sat, May 11, 2002 at 09:21:03AM -0700, Quentin Arce wrote:
> > 
> > 
> > Hello,
> > 
> >     I have been using XFS since if first came out... well a little before
> > that :)
> > 
> > Anyhow, I have just finished running xfs_repair on a x86 build system
> > and found this error twice: 
> > 
> > LEAFN node level is 1 inode 104051713 bno = 8388608
> 
> From a quick look at the code, this seems to be something
> unexpected which xfs_repair does nothing about.  You could
> try recreating that directory (for inode 104051713 -- use
> xfs_ncheck -i to find the full path to the inode).
> 
> > Please if you know what this means please let me know... Seem it was not
> > repaired on the first pass with xfs_repair.
> > 
> > Also one other question regarding xfs_repair... This system as well as
> > my laptop seem to always rebuild inode 128.  Is their a reason why this
> > is rebuilt on some systems but not others?
> 
> 128 is usually the root inode in a 4K bsize filesystem -- if you
> are re-running repair and the lost+found directory is re-created
> each time, then this directory will need to be reconstructed.
> 
> cheers.
> 
> --
> Nathan



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