All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Alex Elder <elder@kernel.org>,
	xfs@oss.sgi.com
Subject: Re: XFS corruption on post 3.7 tree.
Date: Thu, 13 Dec 2012 16:41:19 -0600	[thread overview]
Message-ID: <20121213224119.GU30652@sgi.com> (raw)
In-Reply-To: <20121213221057.GA22049@redhat.com>

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

  reply	other threads:[~2012-12-13 22:41 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
2012-12-13 22:41   ` Ben Myers [this message]
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=20121213224119.GU30652@sgi.com \
    --to=bpm@sgi.com \
    --cc=davej@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.