linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Cc: Ric Wheeler <rwheeler@redhat.com>, Justin Maggard <jmaggard10@gmail.com>
Subject: Re: [PATCH] libext2fs: use proper functions to set/clear block group flags
Date: Wed, 02 Sep 2009 16:15:23 -0500	[thread overview]
Message-ID: <4A9EE06B.5010500@redhat.com> (raw)
In-Reply-To: <4A9ED75A.7030406@redhat.com>

Eric Sandeen wrote:
> As Justin & Ric reported, something like this on a
> 22T (sparse) bigfile:
> 
> 	e2fsprogs/misc/mke2fs -E lazy_itable_init=1 \
> 			      -O uninit_bg -b 4096 bigfile
> 	mount -o loop bigfile mnt/
> 	for I in `seq 1 5`; do mkdir mnt/$I; done
> 	umount mnt/
> 	e2fsprogs/e2fsck/e2fsck -f bigfile
> 
> would give us corrupted block group checksums:
> 
> 	<other problems related to uninit snipped>
> 	One or more block group descriptor checksums are invalid.  Fix<y>? yes
> 
> 	Group descriptor 6301 checksum is invalid.  FIXED.
> 	Group descriptor 7799 checksum is invalid.  FIXED.
> 
> There wer=re a few places which accessed bg_flags directly 
> rather than using the helper functions; fixing these seems
> to resolve the problem.

Well, it resolves that problem, but further testing reveals another
lurking behind it, so expect more patches ;)

-Eric

  reply	other threads:[~2009-09-02 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 20:36 [PATCH] libext2fs: use proper functions to set/clear block group flags Eric Sandeen
2009-09-02 21:15 ` Eric Sandeen [this message]
2009-09-02 21:26   ` Justin Maggard
2009-09-02 21:36 ` [PATCH V2] " Eric Sandeen
2009-09-06 16:29   ` 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=4A9EE06B.5010500@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jmaggard10@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 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).