public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: benediktibk@aon.at
Cc: Benedikt Schmidt <benedikt.schmidt@tum.de>, xfs@oss.sgi.com
Subject: Re: xfs_repair force_geometry
Date: Mon, 13 May 2013 17:15:14 -0500	[thread overview]
Message-ID: <519165F2.80902@sandeen.net> (raw)
In-Reply-To: <5190DB7F.2050505@tum.de>

On 5/13/13 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. 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.

the geometry in "force_geometry" refers to the filesystem geometry,
not the CHS geometry of your disk.

It's only needed if the fs has only 2 allocation groups and they don't
match, or if the fs has only a single allocation group (and therefore
has nothing to test against).

So I don't think that's the option you need.

I don't know what you copied the fs to, but perhaps you copied the
entire disk, not the partition.  

How did you invoke dd_rescue?

If you dd_rescued to a file, what does:

# file <file you dd'd to>

say?

Or, if you dd_rescued to a device, what does

# file -s <dev you dd'd to>

say?

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-05-13 22:15 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
2013-05-13 22:15 ` Eric Sandeen [this message]
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=519165F2.80902@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=benedikt.schmidt@tum.de \
    --cc=benediktibk@aon.at \
    --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