[Top] [All Lists]

Re: A corruption that seems to span a few kernels

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: A corruption that seems to span a few kernels
From: Joe Landman <landman@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 03 Feb 2012 16:31:16 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20120203212724.GA22100@xxxxxxxxxxxxx>
Organization: Scalable Informatics
References: <4F2C3D46.1010509@xxxxxxxxxxxxxxxxxxxxxxx> <20120203212724.GA22100@xxxxxxxxxxxxx>
Reply-to: landman@xxxxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0
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 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,, 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

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.



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

<Prev in Thread] Current Thread [Next in Thread>