All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Aurora Henson <vaurora@redhat.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: Ric Wheeler <rwheeler@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: 32TB ext4 fsck times
Date: Thu, 23 Apr 2009 11:14:26 -0400	[thread overview]
Message-ID: <20090423151426.GC8476@shell> (raw)
In-Reply-To: <10808.1240466476@gamaville.dokosmarshall.org>

On Thu, Apr 23, 2009 at 02:01:16AM -0400, Nick Dokos wrote:
> Valerie Aurora Henson <vaurora@redhat.com> wrote:
> 
> > Back to something useful the short term... Was the file system created
> > with uninitialized block groups and lazy inode table initialization?
> > 
> 
> Uninit_bg was on but lazy inode table initialization was off.  I tried
> turning lazy_itable_init on but e2fsck gets tons of errors, starting
> with group descriptor checksum errors.  Unfortunately, I now get group
> descriptor checksum errors even without lazy_itable_init and I 'm not
> sure why. So I'm back to debugging mke2fs/e2fsck.

I ran into a few heisenbugs when I was working on this, and there's
still that one failing test.  I did track down the commit that started
it, it was:

commit de119e26eb2cf041a8365994dc3a32efc080682e
Author: Valerie Aurora Henson <vaurora@redhat.com>
Date:   Tue Feb 3 13:15:19 2009 -0800

    e2fsck: Miscellaneous e2fsck-related 64-bit fixes.

    With this change, e2fsck runs to completion on a minimal 33-bit file system.

    Signed-off-by: Valerie Aurora Henson <vaurora@redhat.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

I might take a look at the problem with the block group descriptors
and lazy itables; that was some crazy^Wcomplex code.

-VAL

      reply	other threads:[~2009-04-23 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  4:06 (unknown), Nick Dokos
2009-04-21 19:31 ` 32TB ext4 fsck times Ric Wheeler
2009-04-21 19:38   ` Eric Sandeen
2009-04-22 23:18   ` Valerie Aurora Henson
2009-04-23  6:01     ` Nick Dokos
2009-04-23 15:14       ` Valerie Aurora Henson [this message]

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=20090423151426.GC8476@shell \
    --to=vaurora@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nicholas.dokos@hp.com \
    --cc=rwheeler@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.