linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: Ric Wheeler <rwheeler@redhat.com>,
	linux-ext4@vger.kernel.org, "Ted Ts'o" <tytso@thunk.org>
Subject: Re: large file system & high object count testing
Date: Mon, 31 Aug 2009 17:13:31 -0600	[thread overview]
Message-ID: <20090831231331.GJ4197@webber.adilger.int> (raw)
In-Reply-To: <150c16850908311425vbc1c0a1if2a7d8ed56f650f5@mail.gmail.com>

On Aug 31, 2009  14:25 -0700, Justin Maggard wrote:
> On Aug 31, 2009  13:02 -0400, Ric Wheeler wrote:
> > Mount after fsck:
> > Aug 31 12:27:12 megadeth kernel: EXT4-fs (dm-75):
> > ext4_check_descriptors: Checksum for group 487 failed (59799!=46827)
> > Aug 31 12:27:12 megadeth kernel: EXT4-fs (dm-75): group descriptors
> > corrupted!
> 
> Ah, so it's not just me.  It looks like you're seeing the exact same
> thing I reported a few days ago in the ">16TB issues" thread.  You
> don't even have to do anything fancy to make this happen.  My test
> case involves simply creating 5 directories on the newly-created
> 64-bit filesystem, and running e2fsck on it immediately after
> unmounting to get the same results.

Justin, could you please replicate this corruption, collecting some
additional information before & after.  My recollection is that the
corruption appears in the first few groups, so 64kB should be plenty
to capture the group descriptor tables (where the checksum is kept).

- mke2fs
- dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-new.gz
- mkdir ...
- sync
- dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-mkdir.gz
- umount
- dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-umount.gz
- e2fsck
- dd if=/dev/XXX bs=4k count=16 | gzip -9 > /tmp/gdt-e2fsck.gz

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-08-31 23:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 16:34 large file system & high object count testing Ric Wheeler
2009-08-31 17:02 ` Ric Wheeler
2009-08-31 20:56   ` Andreas Dilger
2009-08-31 21:02     ` Ric Wheeler
2009-08-31 21:25       ` Justin Maggard
2009-08-31 22:20         ` Ric Wheeler
2009-08-31 23:13         ` Andreas Dilger [this message]
2009-08-31 23:37           ` Justin Maggard
2009-09-02  9:15             ` Andreas Dilger
2009-08-31 20:19 ` Andreas Dilger
2009-08-31 21:01   ` Ric Wheeler
2009-08-31 23:16     ` Andreas Dilger

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=20090831231331.GJ4197@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=jmaggard10@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=tytso@thunk.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).