From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: how to decode metadump info produced by xfs_db, and superblock error
Date: Sat, 29 Jan 2011 18:56:06 -0600 [thread overview]
Message-ID: <4D44B726.8090409@hardwarefreak.com> (raw)
In-Reply-To: <SNT130-w5507ED619ADEE5A0761FA4DAE30@phx.gbl>
lord worm put forth on 1/29/2011 6:25 PM:
>
> 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).
>
> xfs_repair fails to fix it, how should I attach the 55M metadata file to this email (do we have an upload location for this?), max size on hotmail is 25M ...
>
> Does the superblock error refer to primary or secondary superblocks? Does xfs_repair attempt to clone the broken superblock from the others?
dd is not a proper XFS filesystem backup/restore utility. Instead use xfsdump
and xfsrestore, or any file level backup/restore solution.
You obviously now know why you shouldn't use dd for this purpose with XFS. ;)
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-30 0:53 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 [this message]
2011-01-30 7:16 ` Dave Chinner
[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=4D44B726.8090409@hardwarefreak.com \
--to=stan@hardwarefreak.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 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.