[Top] [All Lists]

Re: xfs_repair 3.2.0 cannot (?) fix fs

To: xfs@xxxxxxxxxxx
Subject: Re: xfs_repair 3.2.0 cannot (?) fix fs
From: Arkadiusz MiÅkiewicz <arekm@xxxxxxxx>
Date: Sat, 28 Jun 2014 23:52:56 +0200
Cc: Alex Elder <elder@xxxxxxxxxx>
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=yHH2egFhd8sb+s7DcFbbuMJiKLerouI8shyuMpwJfWk=; b=PkBGnuMU3je7WSGqOZJZZmKTBbt5rh1CDnTIsnS1IR3pYZDb5KkKdBOSJCLU0yYew7 ntV/SaUzgOMyymCALJPwkT+qHGPOxFJN3qFVOa8RywnMiPaohQ+5Usizo+8dfUr0RoFn dX8AX3MVtoFmQExVNuviG92vLKDDs8w+BKWbQ=
In-reply-to: <201406280141.54350.arekm@xxxxxxxx>
References: <201406280141.54350.arekm@xxxxxxxx>
User-agent: KMail/1.13.7 (Linux/3.16.0-rc2-00211-gd7933ab; KDE/4.13.2; x86_64; ; )
On Saturday 28 of June 2014, Arkadiusz MiÅkiewicz wrote:
> Hello.
> I have a fs (metadump of it
> http://ixion.pld-linux.org/~arekm/p2/x1/web2-home.metadump.gz)
> that xfs_repair 3.2.0 is unable to fix properly.
> Running xfs_repair few times shows the same errors repeating:
> http://ixion.pld-linux.org/~arekm/p2/x1/repair2.txt
> http://ixion.pld-linux.org/~arekm/p2/x1/repair3.txt
> http://ixion.pld-linux.org/~arekm/p2/x1/repair4.txt
> http://ixion.pld-linux.org/~arekm/p2/x1/repair5.txt
> (repair1.txt also exists - it was initial, very big/long repair)
> Note that fs mounts fine (and was mounting fine before and after repair)
> but xfs_repair indicates that not everything got fixed.
> Unfortunately there looks to be a problem with metadump image. xfs_repair
> is able to finish fixing on a restored image but is not able (see
> repairX.txt) above on real devices. Huh?

Made xfs metadump without file obfuscation and I'm able to reproduce the 
problem reliably on the image (if some xfs developer wants metadump image then 
please mail me - I don't want to put it for everyone due to obvious reasons).

So additional bug in xfs_metadump where file obfuscation "fixes" some issues. 
Does it obfuscate but keep invalid conditions (like keeping "/" in file name) 
? I guess it is not doing that.

CC: Alex as he did obfuscation algorithm rewrite at some point.

Anyway repair logs for that metadump

Arkadiusz MiÅkiewicz, arekm / maven.pl

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