On Tue, Feb 07, 2012 at 11:33:11AM -0800, Keith Keller wrote:
> Hi XFS list,
> I'm having some strange trouble with xfs_repair and xfs_metadump, which
> I am hoping you can help with. I have an xfs filesystem which is backed
> by an mdraid/LVM combination. Recently two drives failed in the RAID6,
> then during the rebuild another disk failed. I was able to salvage the
> array by using ddrescue to copy the failed drive to a new drive (only
> 8k were lost). Once I did that, I turned to xfs_repair to check that
> the filesystem was okay.
> So far, it has reported a large number of errors, but consistently gets
> stuck during phase 3. I have used xfsprogs 3.1.7 as well as the latest
> clone from git, and have also used -P and not used -P, with no luck. I
> have saved stderr, but it is extremely large. Nothing obvious
> distinguishes the last stderr messages from previous messages, where it
> might indicate why xfs_repair has stalled. (I can post stderr or make
> it available by HTTP if it helps.)
> On 2012-02-07, Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > So far, it has reported a large number of errors, but consistently gets
> > stuck during phase 3.
> I am not at all clear on what happened, but xfs_repair is no longer
That sounds like you've got dodgy storage to me (e.g. losing an IO),
or that it just took a long time to process something.
> The downside is, it's finding a huge number of problems on the
> filesystem. What are the odds that the fs is actually usable when the
> repair completes? It's hard to imagine a repair that generates ~2GB of
> output on stderr could be good news (so far; granted I did use -v).
Not good if there are lots of problems. Indeed, even losing 8k can
cause serious problems if that 8k is in siginificant indexes and
they are too damaged to be recovered. That has cascade effects and
usually results in lots of stuff in lost+found. Without knowing
what the corruption is or seeing the output, that's the best I can
> xfs mailing list