From: Andreas Dilger <adilger@clusterfs.com>
To: Avantika Mathur <mathur@linux.vnet.ibm.com>
Cc: Girish Shilamkar <girish@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] uninitialized groups ported - kernel
Date: Fri, 22 Jun 2007 10:04:54 -0600 [thread overview]
Message-ID: <20070622160454.GM5181@schatzie.adilger.int> (raw)
In-Reply-To: <467B0FA6.1090509@linux.vnet.ibm.com>
On Jun 21, 2007 16:54 -0700, Avantika Mathur wrote:
> Kernel build was failing with the uninitialized patches when
> CONFIG_CRC16=m. The patch below resolves this issue.
No patch?
> Also, when testing the patches, filesystem mount fails:
>
> EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 1
> failed (0!=1)
>
> EXT4-fs: group descriptors corrupted!
>
> EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 7
> failed (0!=1)
>
> Even though the uninitgrps feature is not enabled, the gdp->bg_checksum
> on disk is nonzero.
Can you figure out why the on-disk checksum is non-zero? That should not
happen. Is it possible that the kernel patch and e2fsprogs somehow have
the wrong struct alignment? Is mke2fs not zeroing out the on-disk data -
the error is reporting that bg_checksum on disk is 1 when it should be 0?
I suppose it is possible for the patch to just ignore the on-disk data if
checksums are not enabled, but we didn't have any such problems in the past...
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-06-22 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 17:48 [PATCH] uninitialized groups ported - kernel Avantika Mathur
2007-06-05 18:48 ` Eric Sandeen
2007-06-05 21:20 ` Andreas Dilger
2007-06-19 4:04 ` Avantika Mathur
2007-06-19 7:50 ` Andreas Dilger
2007-06-20 11:56 ` Girish Shilamkar
2007-06-21 17:37 ` Andreas Dilger
2007-06-21 23:54 ` Avantika Mathur
2007-06-22 16:04 ` Andreas Dilger [this message]
2007-06-22 16:20 ` Dave Kleikamp
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=20070622160454.GM5181@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=girish@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.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