| To: | Dave Jones <davej@xxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, Alex Elder <elder@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS corruption on post 3.7 tree. |
| From: | Ben Myers <bpm@xxxxxxx> |
| Date: | Thu, 13 Dec 2012 16:41:19 -0600 |
| In-reply-to: | <20121213221057.GA22049@xxxxxxxxxx> |
| References: | <20121213205522.GA28455@xxxxxxxxxx> <20121213221057.GA22049@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
Hi Dave,
On Thu, Dec 13, 2012 at 05:10:57PM -0500, Dave Jones wrote:
> On Thu, Dec 13, 2012 at 03:55:22PM -0500, Dave Jones wrote:
> > Doing a kernel build while running on a 3.7+ tree from last night and I
> hit this...
> >
> >
> > [22637.787422] XFS: Internal error XFS_WANT_CORRUPTED_RETURN at line 163
> of file fs/xfs/xfs_dir2_data.c. Caller 0xffffffffa070086a
Looks like the dir v2 verifier found that a single block directory had a data
entry without a corresponding leaf entry in the block.
> I unmounted, remounted, unmounted, and then ran xfs_repair on it, as prompted.
> xfs_repair noted..
>
> bad hash table for directory inode 201328949 (bad stale count): rebuilding
Interesting!
> After remounting, things seemed ok again.
> I blew away my .ccache on that drive, and restarted my compile,
> and then hit the same bug again.
Suppose you could you grab a metadump before repairing it next time?
Regards,
Ben
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Bug#695875: xfsprogs: Build-Depend on libreadline6 rather than libreadline5, Nathan Scott |
|---|---|
| Next by Date: | Re: [PATCH] xfsprogs: Fix possible unallocated memory access in fiemap, Dave Chinner |
| Previous by Thread: | Re: XFS corruption on post 3.7 tree., Dave Jones |
| Next by Thread: | Re: XFS corruption on post 3.7 tree., Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |