linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jeremy Sanders <jss@ast.cam.ac.uk>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4: Group descriptors look bad... trying backup blocks...
Date: Fri, 17 Apr 2009 12:00:29 -0500	[thread overview]
Message-ID: <49E8B5AD.6030907@redhat.com> (raw)
In-Reply-To: <gs9nm5$8m1$1@ger.gmane.org>

Jeremy Sanders wrote:
> Hi - I'm trying out ext4 on a large 8.2 TB software raid device (md). On 
> rebooting (cleanly unmounting), I tried an fsck on the device. I get the 
> following:
> 
> [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>?
> 
> It then finds lots of bad group descriptors.
> 
> This is Fedora 10, 2.6.27.21-170.2.56.fc10.x86_64 and 
> e2fsprogs-1.41.4-4.fc10.x86_64.
> 

Jeremy, if you're willing, could you upgrade to the 2.6.29 kernel that's
in F10 updates-testing?  That way the ext4 code is a bit more of a
recent, common codebase.  Also, if this is a test fs, re-mkfs'ing from
scratch might not be a bad way to go.

Depending on how hard it is to reproduce, it may also be interesting to
try a filesystem just shy of 8TB (2^31) blocks in case there is some
32-bit wrap-around there, since you're at 8.2T....

-Eric

  parent reply	other threads:[~2009-04-17 17:00 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 [this message]
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
     [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=49E8B5AD.6030907@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jss@ast.cam.ac.uk \
    --cc=linux-ext4@vger.kernel.org \
    /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).