From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair force_geometry
Date: Mon, 13 May 2013 12:56:07 -0500 [thread overview]
Message-ID: <51912937.4030404@hardwarefreak.com> (raw)
In-Reply-To: <5190DB7F.2050505@tum.de>
On 5/13/2013 7:24 AM, Benedikt Schmidt wrote:
> Hi,
> currently I'm looking for the correct usage of the force_geometry option
> of xfs_repair. I wasn't able to find more documentation on this option
> beside that it exists. Could please somebody explain it to me?
> For a more detailed description of my problem: I've got here a hard disk
> which is dying at the moment, so I copied all the content with dd_rescue
> to a new and bigger one. To use xfs_copy wasn't possible as the
> filesystem was already corrupted.
This is a standalone disk which wholly contains an XFS filesystem, yes?
The filesystem is corrupted and cannot be repaired? And it won't mount?
> So now I've got nearly everything on
> the second hard disk (dd_rescue could'nt copy something around 6 or 7
> MB), but I can not mount the filesystem or even run xfs_repair on it, as
> it fails to find a superblock. I think the problem lies in the fact that
> the new disk has a different geometry than the previous one.
Given the fact that the filesystem is already corrupted and not
repairable, and the disk is in a state of failure, it's not surprising
you can't repair or mount after the ddrescue copy, which now contains
the same corrupted structures.
If the original can't be repaired nor mounted, why would you believe a
sector-by-sector copy could be?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-13 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 12:24 xfs_repair force_geometry Benedikt Schmidt
2013-05-13 16:58 ` Michael L. Semon
2013-05-13 17:56 ` Stan Hoeppner [this message]
2013-05-13 22:15 ` Eric Sandeen
2013-05-14 5:11 ` Benedikt Schmidt
2013-05-14 7:50 ` Michael L. Semon
2013-05-14 8:56 ` Benedikt Schmidt
2013-05-14 12:35 ` Stan Hoeppner
2013-05-14 17:54 ` Michael L. Semon
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=51912937.4030404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox