From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Cc: Alex Elder <elder@kernel.org>
Subject: Re: xfs_repair 3.2.0 cannot (?) fix fs
Date: Sat, 28 Jun 2014 23:52:56 +0200 [thread overview]
Message-ID: <201406282352.56431.arekm@maven.pl> (raw)
In-Reply-To: <201406280141.54350.arekm@maven.pl>
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
http://ixion.pld-linux.org/~arekm/p2/x2/repair-no-obfuscation1.txt
http://ixion.pld-linux.org/~arekm/p2/x2/repair-no-obfuscation2.txt
--
Arkadiusz Miśkiewicz, arekm / maven.pl
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-28 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 23:41 xfs_repair 3.2.0 cannot (?) fix fs Arkadiusz Miśkiewicz
2014-06-28 21:52 ` Arkadiusz Miśkiewicz [this message]
2014-06-28 22:01 ` Arkadiusz Miśkiewicz
2014-06-30 3:18 ` Dave Chinner
2014-06-30 3:44 ` Dave Chinner
2014-06-30 5:36 ` Arkadiusz Miśkiewicz
2014-06-30 11:12 ` Dave Chinner
2014-06-30 11:53 ` Arkadiusz Miśkiewicz
2014-06-30 12:06 ` Dave Chinner
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=201406282352.56431.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=elder@kernel.org \
--cc=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