From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC] properly lock group descriptors before initializing
Date: Wed, 16 Jul 2008 00:36:09 -0500 [thread overview]
Message-ID: <487D88C9.4050501@redhat.com> (raw)
In-Reply-To: <487D8671.2080307@redhat.com>
Eric Sandeen wrote:
> I noticed when filling a 1T filesystem with 4 threads using the
> fs_mark benchmark:
>
> fs_mark -d /mnt/test -D 256 -n 100000 -t 4 -s 20480 -F -S 0
>
> that I occasionally got checksum mismatch errors:
>
> EXT4-fs error (device sdb): ext4_init_inode_bitmap: Checksum bad for group 6935
>
> etc. I'd reliably get 4-5 of them during the run.
>
> It appears that the problem is likely a race to init the bg's
> when the uninit_bg feature is enabled.
>
> With the patch below I was able to complete 2 runs with no errors
> or warnings. However, I did hit a hang on one run that I can't yet
> explain, so maybe this bears more inspection or testing.
Crud hit it again, looks like it's my fault. So hold off on this one :)
-Eric
next prev parent reply other threads:[~2008-07-16 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 5:26 [PATCH, RFC] properly lock group descriptors before initializing Eric Sandeen
2008-07-16 5:36 ` Eric Sandeen [this message]
2008-07-16 9:03 ` Andreas Dilger
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=487D88C9.4050501@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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