| To: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: agi unlinked bucket |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 25 Aug 2008 10:39:29 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.1.10.0808231412230.20126@xxxxxxxxxxxxxxxxxx> |
| Mail-followup-to: | Christian Kujau <lists@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <alpine.DEB.1.10.0808230017150.20126@xxxxxxxxxxxxxxxxxx> <alpine.DEB.1.10.0808231412230.20126@xxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Sat, Aug 23, 2008 at 02:14:06PM +0200, Christian Kujau wrote: > On Sat, 23 Aug 2008, Christian Kujau wrote: >> # xfs_repair -V >> xfs_repair version 2.9.8 > > The same errors occur when running with xfs_check from the latest CVS > checkout :-\ > >> # blockdev --getsize64 /dev/mapper/md3 >> 147445706752 >> # xfs_check /dev/mapper/md3 >> agi unlinked bucket 26 is 20208090 in ag 0 (inode=20208090) >> link count mismatch for inode 128 (name ?), nlink 333, counted 334 >> link count mismatch for inode 20208090 (name ?), nlink 0, counted 1 >> Command exited with non-zero status 3 > > Anybody? If you do a mount then unmount then rerun xfs-check, does it go away? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs shutdown with 2.6.27-rc4, Nagy Zoltan |
|---|---|
| Next by Date: | Re: [2.6.27-rc4] XFS i_lock vs i_iolock..., Dave Chinner |
| Previous by Thread: | Re: agi unlinked bucket, Christian Kujau |
| Next by Thread: | Re: agi unlinked bucket, Christian Kujau |
| Indexes: | [Date] [Thread] [Top] [All Lists] |