From: Dave Chinner <david@fromorbit.com>
To: lord worm <cryptopsy@live.com>
Cc: xfs@oss.sgi.com
Subject: Re: how to decode metadump info produced by xfs_db, and superblock error
Date: Sun, 30 Jan 2011 18:16:30 +1100 [thread overview]
Message-ID: <20110130071630.GE21311@dastard> (raw)
In-Reply-To: <SNT130-w5507ED619ADEE5A0761FA4DAE30@phx.gbl>
On Sat, Jan 29, 2011 at 07:25:10PM -0500, lord worm wrote:
>
> What kind of information is in this file produced by metadump, is it worth reading it somehow?
>
> I'm trying to first understand what's causing a 'superblock cannot
> be read' error in my XFS after a succesfully dd of the partition
> (dd succeeds in copying to a file, and also restoring, but after
> restoring it cannot mount).
dmesg output when the mount fails?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-30 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 0:25 how to decode metadump info produced by xfs_db, and superblock error lord worm
2011-01-30 0:48 ` FW: " lord worm
2011-01-30 0:56 ` Stan Hoeppner
2011-01-30 7:16 ` Dave Chinner [this message]
[not found] ` <SNT130-w23319C8BC652352929903ADAE30@phx.gbl>
[not found] ` <20110130214026.GF21311@dastard>
[not found] ` <SNT130-w32CA503F4940DD51CBE1A3DAE20@phx.gbl>
2011-01-31 3:51 ` 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=20110130071630.GE21311@dastard \
--to=david@fromorbit.com \
--cc=cryptopsy@live.com \
--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