From: Guest section DW <dwguest@win.tue.nl>
To: "Ville Holma" <ville.holma@pp.htv.fi>, <linux-kernel@vger.kernel.org>
Subject: Re: a way to restore my hd ?
Date: Sun, 22 Apr 2001 00:30:13 +0200 [thread overview]
Message-ID: <20010422003013.A18236@win.tue.nl> (raw)
In-Reply-To: <000701c0ca7b$051934a0$6786f3d5@pp.htv.fi>
In-Reply-To: <000701c0ca7b$051934a0$6786f3d5@pp.htv.fi>; from Ville Holma on Sat, Apr 21, 2001 at 06:52:01PM +0300
On Sat, Apr 21, 2001 at 06:52:01PM +0300, Ville Holma wrote:
> EXT2-fs: #blocks per group too big: 2147516416
> debian:~# e2fsck /dev/hdb7
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> Corruption found in superblock. (frags_per_group = 2147516416).
> debian:~# e2fsck -b -2147450879 /dev/hdb7
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> e2fsck: Attempt to read block from filesystem resulted in short read while
> trying to open /dev/hdb7
(1) e2fsck is very good at correcting minor problems. But if something
really bad happened, e2fsck will make matters only worse. If your data
is valuable, keep e2fsck far away. (For example, make a copy with dd
before starting to fiddle with the disk contents.)
(2) No doubt you do not really have a disk with over 2^31 blocks,
so this suggestion from e2fsck is just a bug in e2fsck.
Maybe -b 32768 would have been more successful.
It might be interesting to look at the contents of the superblock
to see what kind of corruption occurred. Bad memory tends to change
a single bit. Here your data suggests more than one corrupted bit.
With disk I/O problems one often sees lots of errors - maybe blocks
with all zeros or all ones, or all data shifted by one or more bits, etc.
next prev parent reply other threads:[~2001-04-21 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 15:52 Ville Holma
2001-04-21 16:40 ` Karsten Keil
2001-04-21 18:27 ` Steve Bromwich
2001-04-21 22:30 ` Guest section DW [this message]
2001-04-21 23:10 ` Alan Cox
2001-04-22 18:17 ` Ville Holma
2001-04-21 16:09 Ville Holma
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=20010422003013.A18236@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.holma@pp.htv.fi \
/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
all inboxes | Powered by JetHome®