From: Eric Sandeen <sandeen@redhat.com>
To: Christian Ohm <chr.ohm@gmx.net>
Cc: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org
Subject: Re: How to recover a damaged ext4 file system?
Date: Sat, 07 Feb 2009 13:04:06 -0600 [thread overview]
Message-ID: <498DDB26.3080102@redhat.com> (raw)
In-Reply-To: <20090207162725.GA27086@moongate.localnet>
Christian Ohm wrote:
> On Tuesday, 6 January 2009 at 14:34, Theodore Tso wrote:
>> It looks like both the primary and the backup block group descriptors
>> are bad. I'm not sure how this happened; normally nothing touches the
>> backup block superblocks at all. Stupid question --- are you sure the
>> partition table is sane; that's always the first thing to check.
>
> I created a new partition on the second drive, and I hope I used exactly the
> same options. The result of fdisk -l is the following:
>
> corrupted drive:
>
> Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0xaaaaaaaa
>
> Device Boot Start End Blocks Id System
> /dev/sde1 1 121601 976760032 83 Linux
>
> new partition on similar drive:
>
> Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0xaaaaaaaa
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 121601 976760001 83 Linux
>
> The only difference is the number of blocks of the partition, I guess since the
> start and end are the same this should be equal as well.
that's counting "cylinders" - try "fdisk -u" to be able to display (or
specify) geometry in sectors, which is not a unit open to interpretation...
-Eric
next prev parent reply other threads:[~2009-02-07 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:53 How to recover a damaged ext4 file system? Christian Ohm
2009-01-06 12:05 ` Andreas Dilger
2009-01-06 19:34 ` Theodore Tso
2009-01-07 21:42 ` Christian Ohm
2009-01-08 10:11 ` Andreas Dilger
2009-02-07 16:27 ` Christian Ohm
2009-02-07 19:04 ` Eric Sandeen [this message]
2009-02-12 21:36 ` Christian Ohm
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=498DDB26.3080102@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=chr.ohm@gmx.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).