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 16:40:18 -0600 [thread overview]
Message-ID: <4963DDD2.4030501@sandeen.net> (raw)
In-Reply-To: <b75ef8170901061431i68f8ebdey3ab08ea3dec9c079@mail.gmail.com>
Gergely Soos wrote:
> Eric,
> your intuition was absolutely correct. The starting point of my
> partition was moved only not up but down 63 sectors (63*512 bytes)
> It all makes sense, the whole partition grew 63*512 bytes = 0x7E (126)
> inodes that is why I found the root inode on inode 0xFE instead of 0x80.
> Now the question remains how the hell should I move it back??
> And what kind of an idiot program moves the partition table without any
> confirmation? That would kill any filesystem.
Strangely, I've seen this before. No idea why, or what is doing it.
Hopefully you have saved copies of all the things you edited & dd'd? So
I'd start by putting those back.
Then you can use a partition editor to move the start of the partition
back where it belongs, I guess. (w/o seeing where you found the
superblocks, I'm not certain).
Or, if I'm reading you right, do you mean that the first "XFSB" is 63
sectors ahead of the start of hdd1? If so, then maybe mounting /dev/hdd
(not /dev/hdd1) just works.
-Eric
> Gergely
>
> On Tue, Jan 6, 2009 at 11:54 PM, Eric Sandeen <sandeen@sandeen.net
> <mailto:sandeen@sandeen.net>> wrote:
>
> Gergely Soos wrote:
> > That is a good idea, I'm gonna search for the XFSB on the entire disk.
> > I will also give PhotoRec a try if nothing else works.
> > In the meantime, Eric, you can download the metadata from here:
> > http://bluepantherit.net/metadump.bz2
> > It would be real nice from you if you would take a closer look.
> >
> > And one more thing, xfs_check -s /dev/hdd1 prints the following:
> > can't seek in filesystem at bb 58701991023656163
> > can't read agfl block for ag 4082146910
> > can't seek in filesystem at bb 58702015871605112
>
> ... it's basically reading garbage as block numbers, but they are well
> past the end of the device, so failing.
>
> Very confused, it is. :)
>
> -Eric
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-06 23:06 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
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 [this message]
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=4963DDD2.4030501@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