| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | xfsrepair: rebuilding directory inode 128 |
| From: | Christian Guggenberger <Christian.Guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 9 Apr 2003 12:02:52 +0200 |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
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
- traversal finished ... - traversing all unattached subtrees
... - traversals finished ... - moving disconnected inodes to
lost+found ...
maybe this issue correlates to Bug230?
Kernel 2.4.20 (xfs-snapshots from Jan to April behave in the same way)
xfsprogs-2.3.11
thanks Christian |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: using lseek() on large files, Chris Wedgwood |
|---|---|
| Next by Date: | Re: Automatic detection of O(1) scheduler in latest kdb, Nicholas Wourms |
| Previous by Thread: | FWD: fsck in background?, Greg Freemyer |
| Next by Thread: | Re: xfsrepair: rebuilding directory inode 128, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |