From: Bernd Schubert <bschubert@ddn.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Bernd Schubert <bs_lists@aakef.fastmail.fm>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Andreas Dilger <andreas.dilger@oracle.com>
Subject: Re: [PATCH] make ext4_valid_block_bitmap() more verbose
Date: Mon, 15 Nov 2010 20:22:58 +0100 [thread overview]
Message-ID: <4CE18892.9020908@ddn.com> (raw)
In-Reply-To: <4CE15DF8.4030600@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On 11/15/2010 05:21 PM, Eric Sandeen wrote:
> On 11/12/10 5:26 PM, Bernd Schubert wrote:
>> The real issue we want to debug with the patch below actually came up while
>> stress testing Lustre using the RHEL5.5 kernel (so 2.6.32'ish ext4), but a
>> more verbose error function should not hurt for vanilla ext4 either.
>>
>> make ext4_valid_block_bitmap() more verbose
>>
>> While running our stress test suite, ext4_valid_block_bitmap()
>> frequently complains about an invalid block bitmap.
>> However, e2fsck does not find anything. So in oder to be able
>> to better debug this issue, make the function more verbose and
>> let it complain about the two possible invalid bitmaps.
>
> Making a raw e2image of the problematic filesystem would let us take a
> look at why e2fsck isn't finding problems; unless you plan to fix that
> yourself as well, which is just fine of course. :)
>
I already captured an e2image and will do again on Wednesday, now that I
could reproduce it again with the updated code. Unfortunately no time
before. Will try to check out myself with debugfs first, if there is
really something wrong. It might be a race in the code as well...
Cheers,
Bernd
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2010-11-15 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 23:26 [PATCH] make ext4_valid_block_bitmap() more verbose Bernd Schubert
2010-11-12 23:56 ` Andreas Dilger
2010-11-15 19:15 ` Bernd Schubert
2010-11-15 16:21 ` Eric Sandeen
2010-11-15 19:22 ` Bernd Schubert [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=4CE18892.9020908@ddn.com \
--to=bschubert@ddn.com \
--cc=andreas.dilger@oracle.com \
--cc=bs_lists@aakef.fastmail.fm \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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).