[Top] [All Lists]

Re: [PATCH 0/4] repair: fixes for 3.2

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 0/4] repair: fixes for 3.2
From: Arkadiusz MiÅkiewicz <arekm@xxxxxxxx>
Date: Tue, 1 Jul 2014 15:40:56 +0200
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maven.pl; s=maven; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=NbFhqlFJaKyN+u51IVPT7I2pN+ADxVrio6HaKZAc53c=; b=HPL6gKd3wKjJKjQ4/mO3uBzt5Rfbao/dVY5ddEe3V2b0J9q3GqdZ8t3hIJzJ+OOXsI IGTZiCbiC+VqYY/d7c0V9pybPWa2oAWJC4Gl1wlb4dnuHiNJfVYEcwHoLV88l4f8aVVf ZWIdcOebbO+PQ2DTUaT7k0dq2KjVsOCNZnqKI=
In-reply-to: <1404219296-29302-1-git-send-email-david@xxxxxxxxxxxxx>
References: <1404219296-29302-1-git-send-email-david@xxxxxxxxxxxxx>
User-agent: KMail/1.13.7 (Linux/3.16.0-rc3-00006-g16874b2; KDE/4.13.2; x86_64; ; )
On Tuesday 01 of July 2014, Dave Chinner wrote:
> Hi Arkadiusz,
> These are the fixes I have so far from working through the metadumps
> you supplied me with. The unobfuscated metadump repairs cleanly with
> these patches, but the obfuscated one still has a directory rebuild
> issue that I haven't got to the bottom of yet. That results in
> an error in phase 6 like:
> Metadata corruption detected at block 0x2af84770/0x1000
> name create failed in ino 2306912354 (117), filesystem may be out of space
> It appears that a read verifier is on a recently created
> directory leaf block and that is failing. I'm not yet sure why the
> leaf block is corrupt, nor why the verifier is even being run on it
> seeing as it was only allocated and initialised during the directory
> rebuild. That directory rebuil dfailure is the reason for all the
> disconected inode that end up in lost+found, and I think it's the
> only remaining issue that I need to solve.
> Can you test the patches on you machine and see if you get the same
> results?

Testing on non obfuscated image here.

Most of issues got fixed, first xfs_repair run:

second xfs_repair run (reports no problems):

When trying to mount
"XFS (loop0): Failed to initialize disk quotas."
so this issue left.


Phase 2 - using internal log
        - zero log...
zero_log: head block 2 tail block 2
        - scan filesystem freespace and inode maps...
Metadata CRC error detected at block 0x0/0x200

Is "Metadata CRC error detected at block" expected here? I mean v4 fs, so no 

Thanks a lot for the fixes.

> Cheers,
> Dave.

Arkadiusz MiÅkiewicz, arekm / maven.pl

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