From: Eric Sandeen <sandeen@redhat.com>
To: Thierry Vignaud <tvignaud@mandriva.com>
Cc: Jeremy Sanders <jss@ast.cam.ac.uk>, linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4: Group descriptors look bad... trying backup blocks...
Date: Tue, 21 Apr 2009 10:52:44 -0500 [thread overview]
Message-ID: <49EDEBCC.3030008@redhat.com> (raw)
In-Reply-To: <m2eivm599b.fsf@vador.mandriva.com>
Thierry Vignaud wrote:
> Jeremy Sanders <jss@ast.cam.ac.uk> writes:
>
>> However, the system seems to mostly work, so I recreated the ext4 device,
>> I've just run my backup script again and fsck'd the device. It seems the
>> problem is reproducible with the new kernel:
>>
>> [root@xback2 ~]# fsck /dev/md0
>> fsck 1.41.4 (27-Jan-2009)
>> e2fsck 1.41.4 (27-Jan-2009)
>> fsck.ext4: Group descriptors look bad... trying backup blocks...
>> Group descriptor 0 checksum is invalid. Fix<y>?
>>
>> Looks like there's a real problem in ext4 causing this under certain
>> circumstances (unless an obscure hardware error is somehow giving the same
>> problem).
>>
>> To cause this, all I did was rsync a set of directories to the disk. No hard
>> link trees were created.
>
> For the record, I reproduced this bug with 2.6.30-rc2-git6 on a new
> 1.5Tb disk. Formated as ext4, using relatime, copied 20Gb.
> On reboot, I got such errors.
> The hd was partitionned (all ext4) as:
> / (5Gb) | /usr (20Gb) | /pub (1.5Tb)
>
> The smaller system fses didn't saw those errors.
Can you provide a little more info on how you copied the 20Gb, and
exactly what the errors were?
Thanks,
-Eric
next prev parent reply other threads:[~2009-04-21 15:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 11:03 fsck.ext4: Group descriptors look bad... trying backup blocks Jeremy Sanders
2009-04-17 11:26 ` Jeremy Sanders
2009-04-17 11:56 ` Theodore Tso
2009-04-17 12:16 ` Jeremy Sanders
2009-04-17 17:10 ` Eric Sandeen
2009-04-17 18:51 ` Jeremy Sanders
2009-04-17 12:24 ` Jeremy Sanders
2009-04-17 16:36 ` Theodore Tso
2009-04-17 17:00 ` Eric Sandeen
2009-04-20 9:33 ` Jeremy Sanders
2009-04-20 11:35 ` Theodore Tso
2009-04-20 11:43 ` Jeremy Sanders
2009-04-20 12:48 ` Theodore Tso
2009-04-20 12:54 ` Jeremy Sanders
2009-04-20 14:49 ` Eric Sandeen
2009-04-20 15:51 ` Eric Sandeen
2009-04-20 15:53 ` Jeremy Sanders
2009-04-20 16:26 ` Eric Sandeen
2009-04-20 16:40 ` Jeremy Sanders
2009-04-20 18:28 ` Andreas Dilger
2009-04-20 18:55 ` Jeremy Sanders
2009-04-20 20:45 ` Andreas Dilger
2009-04-22 9:34 ` Jeremy Sanders
2009-04-22 9:07 ` Jeremy Sanders
2009-04-22 9:59 ` Thierry Vignaud
2009-04-24 8:27 ` Jeremy Sanders
2009-04-21 15:14 ` Thierry Vignaud
2009-04-21 15:52 ` Eric Sandeen [this message]
[not found] ` <m23ac255pp.fsf@vador.mandriva.com>
2009-04-21 16:40 ` Eric Sandeen
2009-04-21 16:56 ` Thierry Vignaud
2009-04-21 16:43 ` Theodore Tso
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=49EDEBCC.3030008@redhat.com \
--to=sandeen@redhat.com \
--cc=jss@ast.cam.ac.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=tvignaud@mandriva.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;
as well as URLs for NNTP newsgroup(s).