From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
Ben Myers <bpm@sgi.com>, Alex Elder <elder@kernel.org>,
xfs@oss.sgi.com
Subject: Re: XFS corruption on post 3.7 tree.
Date: Thu, 13 Dec 2012 17:10:57 -0500 [thread overview]
Message-ID: <20121213221057.GA22049@redhat.com> (raw)
In-Reply-To: <20121213205522.GA28455@redhat.com>
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
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
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.
Dave
next prev parent reply other threads:[~2012-12-13 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 20:55 XFS corruption on post 3.7 tree Dave Jones
2012-12-13 22:10 ` Dave Jones [this message]
2012-12-13 22:41 ` Ben Myers
2012-12-13 23:52 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121213221057.GA22049@redhat.com \
--to=davej@redhat.com \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox