From: Christoph Hellwig <hch@infradead.org>
To: Joe Landman <landman@scalableinformatics.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: A corruption that seems to span a few kernels
Date: Fri, 3 Feb 2012 16:27:24 -0500 [thread overview]
Message-ID: <20120203212724.GA22100@infradead.org> (raw)
In-Reply-To: <4F2C3D46.1010509@scalableinformatics.com>
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?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-03 21:27 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 [this message]
2012-02-03 21:31 ` Joe Landman
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=20120203212724.GA22100@infradead.org \
--to=hch@infradead.org \
--cc=landman@scalableinformatics.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox