xfs
[Top] [All Lists]

Re: xfsrepair: rebuilding directory inode 128

To: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfsrepair: rebuilding directory inode 128
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 10 Apr 2003 11:28:06 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1049937908.538.3.camel@bonnie79>
References: <20030409120252.A29309@xxxxxxxxxxxxxxxxxxxxxxxx> <20030409224118.GA759@frodo> <1049937908.538.3.camel@bonnie79>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.3i
On Thu, Apr 10, 2003 at 03:25:08AM +0200, Christian Guggenberger wrote:
> 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)?

The "-i" option to ls(1) will print out inode numbers.

cheers.

-- 
Nathan


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