xfs
[Top] [All Lists]

Re: log recovery fails at mount

To: John Valdes <valdes@xxxxxxx>
Subject: Re: log recovery fails at mount
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 24 Jan 2012 17:03:31 -0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20120124225840.GA20222@xxxxxxxxxxxxxxxxxxxx>
References: <20120124024340.GA6689@xxxxxxxxxxxxxxxxxxxx> <4F1E3C71.1020303@xxxxxxxxxxx> <20120124225840.GA20222@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
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
> 

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