xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Kernel oops / XFS filesystem corruption

from [Mark Goodwin] [Permanent Link][Original]
To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: Kernel oops / XFS filesystem corruption
From: Mark Goodwin <markgw@xxxxxxx>
Date: Mon, 03 Mar 2008 12:02:24 +1100
Cc: Thomas Müller <thomas@xxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <47CA043F.5070202@sandeen.net>
Organization: SGI Engineering
References: <47C93C32.40006@mathtm.de> <47C9C44D.8080400@sandeen.net> <47C9F5E9.70703@mathtm.de> <47CA043F.5070202@sandeen.net>
Reply-to: markgw@xxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.14 (Windows/20071210)


Eric Sandeen wrote:
Thomas Müller wrote:
Eric Sandeen wrote:
Did you also happen to save the xfs_repair output? 
No, but I made a complete copy of the file system before
repairing it, so I can easily recreate it... :)


oh, like a dd image?  great.  You can use xfs_metadump to make a more
transportable image... xfs folks might even be able to use that to
recreate the oops.


YES PLEASE. See the xfs_metadump man page for instructions. It will
obfuscate filenames by default (but please only do so if you need to).

Please make it available for Barry, thanks.

Cheers
-- Mark


[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Kernel oops / XFS filesystem corruption, Barry Naujok
Next by Date:  Re: [REVIEW] Don't make lazy counters default for mkfs, Josef 'Jeff' Sipek
Previous by Thread:  Re: Kernel oops / XFS filesystem corruption, Barry Naujok
Next by Thread:  Re: [REVIEW] Don't make lazy counters default for mkfs, Andi Kleen
Indexes:  [Date] [Thread] [Top] [All Lists]