From: Mark Goodwin <markgw@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Thomas Müller" <thomas@mathtm.de>,
xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel oops / XFS filesystem corruption
Date: Mon, 03 Mar 2008 12:02:24 +1100 [thread overview]
Message-ID: <47CB4E20.5070808@sgi.com> (raw)
In-Reply-To: <47CA043F.5070202@sandeen.net>
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
prev parent reply other threads:[~2008-03-03 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 11:21 Kernel oops / XFS filesystem corruption Thomas Müller
2008-03-01 21:02 ` Eric Sandeen
2008-03-02 0:33 ` Thomas Müller
2008-03-02 1:34 ` Eric Sandeen
2008-03-02 19:02 ` Thomas Müller
2008-03-03 1:02 ` Barry Naujok
2008-03-03 1:02 ` Mark Goodwin [this message]
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=47CB4E20.5070808@sgi.com \
--to=markgw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=thomas@mathtm.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.