public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Gergely Soos <sogerc1@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: need help to repair XFS partition
Date: Tue, 06 Jan 2009 12:40:22 -0600	[thread overview]
Message-ID: <4963A596.70208@sandeen.net> (raw)
In-Reply-To: <b75ef8170901061004n75f52cffg7f810a51aca21ff@mail.gmail.com>

Gergely Soos wrote:
> In my original email there was an attachment that contained the original
> boot sector, but anyway, here comes the hexdump Eric asked for:

Sorry, didn't open the tarfile :)

> 00000000  91 f0 1c 43 90 01 ba bf  f7 ee 29 9a 1e 6c d5 aa
> |.ð.C..º¿÷î)..lÕª|
> 00000010  11 5a 12 cb 3b 29 cb ff  39 ce 4e d3 95 ec b9 39
> |.Z.Ë;)Ëÿ9ÎNÓ.ì¹9|

...

> This looks like nothing to me...

I agree... something splattered on the disk it seems.  How far does this
junk go on, I wonder?

> xfs_repair rejects all superblock candidates and exits saying something
> like: Sorry, cannot find valid secondary superblock.
> I'm not sure what a GPT is, but this is an IDE harddisk, I'm using kernel
> 2.6.20 and my xfs partition is /dev/hdd1

GPT is a disk partitioning scheme, and it puts backups at the end of the
disk (IIRC), which sometimes automatically gets restored to the front.
But this does not look like your case.

> Is there any way xfs_repair would accept the superblock as is and move on
> with the repairs?

Well, you want to be sure it matches.  But - go looking through your
disk for "XFSB" and keep track of where the offsets are; you should find
your backup superblocks that way, and we can use xfs_db to get the
values out and perhaps restore your primary.

(you can probably do this on your own, but something like:
# dd if=/dev/hdd1 bs=4k | hexdump -C | grep XFSB
might do nicely)

xfs_repair should be better at using these by itself.  If you can put
your metadump somewhere that I can get to it, maybe I can look and see
why repair is not succeeding...

-Eric

> Gergely
> 

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

  reply	other threads:[~2009-01-06 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  9:11 need help to repair XFS partition Gergely Soos
2009-01-06  9:27 ` Chris Wedgwood
2009-01-06 16:06 ` Eric Sandeen
2009-01-06 18:04   ` Gergely Soos
2009-01-06 18:40     ` Eric Sandeen [this message]
2009-01-06 18:46     ` Eric Sandeen
     [not found]       ` <b75ef8170901061351madb546flbc1631bc55cd4412@mail.gmail.com>
2009-01-06 21:54         ` Eric Sandeen
2009-01-06 22:31           ` Gergely Soos
2009-01-06 22:40             ` Eric Sandeen
2009-01-06 22:54               ` Gergely Soos
2009-01-06 23:09                 ` Christoph Hellwig
2009-01-06 23:26                   ` Gergely Soos

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=4963A596.70208@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sogerc1@gmail.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