linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
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: Mon, 20 Apr 2009 07:35:34 -0400	[thread overview]
Message-ID: <20090420113534.GR19186@mit.edu> (raw)
In-Reply-To: <gshfgl$o6m$1@ger.gmane.org>

On Mon, Apr 20, 2009 at 10:33:09AM +0100, Jeremy Sanders wrote:
> 
> 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:

When you say reproducible, how many times have you tried it, and were
you able to reproduce it every single time?  50% of time?  I do
believe there is a problem, but we haven't been able to something
where it's easily reproducible.  So if you can easily reproduce this,
this is definitely very exciting.

> [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>?

Do you have to reboot to see this, or is it enough to unmount the
filesystem?  How big is the ext4 filesystem, and how big was the
amount of data that you rsync'ed?  One thing that would be worth
trying if you can easily reproduce is whether it happens on a single
device disk, or whether it only shows up when you use a /dev/mdX
device.

Thanks,

						- Ted

  reply	other threads:[~2009-04-20 11:35 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 [this message]
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=20090420113534.GR19186@mit.edu \
    --to=tytso@mit.edu \
    --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).