Re: xfsrepair: rebuilding directory inode 128

[Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>]

On Thu, 2003-04-10 at 00:41, Nathan Scott wrote:
> On Wed, Apr 09, 2003 at 12:02:52PM +0200, Christian Guggenberger wrote:
> > Hi,
> > 
> > I've been bitten by Bug 230 (umount hangs). Now I noticed, that _every_ 
> > time I run xfs_repair on /usr I get following output in Phase 6:
> > 
> > Phase 6 - check inode connectivity...
> >         - resetting contents of realtime bitmap and summary inodes
> >         - ensuring existence of lost+found directory
> >         - traversing filesystem starting at / ... rebuilding directory 
> >         inode 128
> 
> This is most likely the "lost+found" directory being unlinked
> and recreated every time.  128 will be your root inode.
> 
> >         - traversal finished ...         - traversing all unattached 
> >         subtrees ...         - traversals finished ...         - moving 
> > disconnected inodes to lost+found ... 
> 

Is there a way to double check if it's the directory you mean ( maybe
xfs_db, but I'm not familiar with the whole lotta 'bout that command)?

Christian