All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: Valerie Aurora <vaurora@redhat.com>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org, Nick Dokos <nicholas.dokos@hp.com>,
	Julia Lawall <julia@diku.dk>
Subject: Re: >16TB issues
Date: Fri, 28 Aug 2009 08:40:13 -0400	[thread overview]
Message-ID: <20090828124013.GB16732@mit.edu> (raw)
In-Reply-To: <150c16850908271930x277daa95sdea8c34868f2ce36@mail.gmail.com>

On Thu, Aug 27, 2009 at 07:30:47PM -0700, Justin Maggard wrote:
> I've been testing the latest 64-bit e2fsprogs from the git pu branch
> (kernel.org 2.6.30.5/x86_64) on a 64-bit (~22TB) filesystem for a
> couple days, since it seems like 32-bit e2fsprogs on a 64-bit
> filesystem is going to take a while longer.  I'm able to create and
> check a filesystem without any problem.  I've also run Andreas'
> llverfs utility for a few hours and not had any complaints.  But, I'm
> running into another strange issue.  Here's what I'm doing:
> # mkfs.ext4 /dev/md0
> # mount /dev/md0 /mnt
> # mkdir /mnt/1 /mnt/2 /mnt/3 /mnt/4 /mnt/5
> # umount /mnt
> # fsck.ext4 -C0 -fy /dev/md0
> ** No errors at all at this point.  fsck returns 0. **
> # mount /dev/md0 /mnt
> The last mount command fails, and the kernel log contains:
> EXT4-fs: ext4_check_descriptors: Checksum for group 0 failed (3412!=9428)
> EXT4-fs: group descriptors corrupted!

Um, that's interesting.  What happens if run fsck.ext4 twice?  i.e:

# mkfs.ext4 /dev/md0
# mount /dev/md0 /mnt
# mkdir /mnt/1 /mnt/2 /mnt/3 /mnt/4 /mnt/5
# umount /mnt
# fsck.ext4 -C0 -fy /dev/md0
# fsck.ext4 -C0 -fy /dev/md0

						- Ted


  reply	other threads:[~2009-08-28 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 22:23 >16TB issues Justin Maggard
2009-07-03 14:38 ` Andreas Dilger
2009-07-16 18:04   ` Justin Maggard
2009-07-16 18:59     ` Valerie Aurora
2009-07-21 16:10     ` Andreas Dilger
2009-07-21 18:52       ` Justin Maggard
2009-07-21 18:57         ` Eric Sandeen
2009-07-21 19:21         ` Andreas Dilger
2009-07-22 22:27           ` Justin Maggard
2009-07-27 22:03             ` Valerie Aurora
2009-07-30 22:23             ` Valerie Aurora
2009-08-01  1:24               ` Justin Maggard
2009-08-03 17:20                 ` Valerie Aurora
2009-08-11 21:39                 ` Valerie Aurora
2009-08-11 22:05                   ` Theodore Tso
2009-08-12  1:25                     ` Valerie Aurora
2009-08-12  2:04                       ` Theodore Tso
2009-08-12 17:59                         ` Valerie Aurora
2009-08-28  2:30                           ` Justin Maggard
2009-08-28 12:40                             ` Theodore Tso [this message]
2009-08-28 20:27                               ` Justin Maggard
2009-08-12  4:21 ` Eric Sandeen
2009-08-12  5:35   ` Justin Maggard
2009-08-12 14:12     ` Eric Sandeen

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=20090828124013.GB16732@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=jmaggard10@gmail.com \
    --cc=julia@diku.dk \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nicholas.dokos@hp.com \
    --cc=vaurora@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.