| To: | Timothy Shimmin <tes@xxxxxxx> |
|---|---|
| Subject: | Re: agi unlinked bucket |
| From: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
| Date: | Mon, 25 Aug 2008 17:02:53 +0200 (CEST) |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <48B22659.9050301@xxxxxxx> |
| References: | <alpine.DEB.1.10.0808230017150.20126@xxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.0808231412230.20126@xxxxxxxxxxxxxxxxxx> <20080825003929.GN5706@disturbed> <alpine.DEB.1.10.0808250254380.26780@xxxxxxxxxxxxxxxxxx> <48B22659.9050301@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Alpine 1.10 (DEB 962 2008-03-14) |
On Mon, 25 Aug 2008, Timothy Shimmin wrote: So in your case, it looks like in AG#0 on the 26th element of the array it is pointing to inode# 20208090. Which would infer that inode#20208090 was unlinked but still had references to it at the time the filesystem was not cleanly unmounted (power loss, crash etc..). It looks like for the root directory inode #128 it has a count of 335 but it is finding 336 entries. Thanks for this very interesting explanation, Timothy. I finally ran xfs_repair on the filesystem, twice, now everything seems to be in good shape. If you guys are interested: http://nerdbynature.de/bits/2.6.27-rc3/fsck_md3.log Thanks, Christian. -- BOFH excuse #363: Out of cards on drive D: |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS vs Elevators (was Re: [PATCH RFC] nilfs2: continuous snapshotting file system), Jamie Lokier |
|---|---|
| Next by Date: | xfs_growfs fix backport for 2.6.16.y, Ed Cashin |
| Previous by Thread: | Re: agi unlinked bucket, Timothy Shimmin |
| Next by Thread: | xfs_quota free, Dan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |