All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Landman <landman@scalableinformatics.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@oss.sgi.com
Subject: Re: A corruption that seems to span a few kernels
Date: Fri, 03 Feb 2012 16:31:16 -0500	[thread overview]
Message-ID: <4F2C5224.4080902@scalableinformatics.com> (raw)
In-Reply-To: <20120203212724.GA22100@infradead.org>

On 02/03/2012 04:27 PM, Christoph Hellwig wrote:
> On Fri, Feb 03, 2012 at 03:02:14PM -0500, Joe Landman wrote:
>> XFS file system, built using a 2.6.32.41 kernel.  External journals.
>>
>> repair the file system, mount, turn on gluster (3.2.5), do a find,
>> and get a corruption.  Actually it looks like xfs_repair doesn't fix
>> the problem.
>>
>> Rinse repeat, reproduce.  Works (procedure to generate the
>> corruption) in 2.6.32.41.scalable, 2.6.39.1, 3.2.2
>
> [PATCH v2] repair: update extent count after zapping duplicate blocks
>
> which was sent to the list yesterday should make xfs_repair handle this
> case.
>
> How do you reproduce the corruption?  Just start gluster on a fresh fs
> an do a find?  Any chance you could share command lines used?

It looks like the corruption was just never repaired by xfs_repair. I 
just followed the notes here: 
http://xfs.org/index.php/XFS_FAQ#Q:_How_to_get_around_a_bad_inode_repair_is_unable_to_clean_up 
and got it operational again.  I first blockget -n -i ###  to figure out 
the mapping and let the user know.

I'll grab the patch and apply it.  If this comes up again, I'll report.

To summarize, this was a corruption that xfs_repair didn't fix, so 
fixing it by hand (and rerunning xfs_repair) did.

Thanks!

Joe

-- 
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@scalableinformatics.com
web  : http://scalableinformatics.com
        http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-02-03 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 20:02 A corruption that seems to span a few kernels Joe Landman
2012-02-03 21:27 ` Christoph Hellwig
2012-02-03 21:31   ` Joe Landman [this message]

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=4F2C5224.4080902@scalableinformatics.com \
    --to=landman@scalableinformatics.com \
    --cc=hch@infradead.org \
    --cc=linux-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.