From: Eric Sandeen <sandeen@sandeen.net>
To: John Valdes <valdes@anl.gov>
Cc: xfs@oss.sgi.com
Subject: Re: log recovery fails at mount
Date: Tue, 24 Jan 2012 17:03:31 -0600 [thread overview]
Message-ID: <4F1F38C3.9090409@sandeen.net> (raw)
In-Reply-To: <20120124225840.GA20222@starfish.mcs.anl.gov>
On 1/24/12 4:58 PM, John Valdes wrote:
> On Mon, Jan 23, 2012 at 11:06:57PM -0600, Eric Sandeen wrote:
>> try:
>>
>> # xfs_metadump /dev/md4 md4.metadump
>> # xfs_mdrestore md4.metadump md4.img
>> # xfs_repair -L md4.img
>>
>> that'll repair a metadata image and you can see how much it runs into.
>
> Good suggestion. Here's the result; looks innocuous:
>
<snip reasonable looking repair output>
>
> However, if I loopback mount the img file, the file/directory names in
> the mounted fs are mostly corrupted; that may be expected though since
> it's just a metadata dump/restore?
>
> prompt# mount -r -t xfs -o loop md4.img /mnt
> prompt# ls /mnt
> ??5?z+o??%F_4(?R?.wrhE*] data K?ckw? T?o??n2o?,?0-|K#\o Z?w?9=ol\?7j??1T
>
> Any other suggestions or comments before I let loose xfs_repair -L on
> the real filesystem?
that's because metadump obfuscates filenames by default. There's an option
to keep them in the clear, and then you won't see all that garbage.
-Eric
> John
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-24 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 2:43 log recovery fails at mount John Valdes
2012-01-24 5:06 ` Eric Sandeen
2012-01-24 22:58 ` John Valdes
2012-01-24 23:03 ` Eric Sandeen [this message]
2012-01-24 23:34 ` John Valdes
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=4F1F38C3.9090409@sandeen.net \
--to=sandeen@sandeen.net \
--cc=valdes@anl.gov \
--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