| To: | Christian Guggenberger <Christian.Guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfsrepair: rebuilding directory inode 128 |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Thu, 10 Apr 2003 08:41:18 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030409120252.A29309@pc9391.uni-regensburg.de> |
| References: | <20030409120252.A29309@pc9391.uni-regensburg.de> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
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 ... cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: problem with xfs_fsr, Wessel Dankers |
|---|---|
| Next by Date: | re[2]: FWD: fsck in background?, Greg Freemyer |
| Previous by Thread: | Re: xfsrepair: rebuilding directory inode 128, Christian Guggenberger |
| Next by Thread: | Re: xfsrepair: rebuilding directory inode 128, Christian Guggenberger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |