From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, Shaohua Li <shli@kernel.org>,
Eryu Guan <eguan@redhat.com>
Subject: Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
Date: Wed, 13 Mar 2013 08:32:47 +0100 [thread overview]
Message-ID: <wrfj7glb92lc.fsf@redhat.com> (raw)
In-Reply-To: <20130313103513.350f24f7@notabene.brown> (NeilBrown's message of "Wed, 13 Mar 2013 10:35:13 +1100")
NeilBrown <neilb@suse.de> writes:
> On Tue, 12 Mar 2013 14:45:44 +0100 Jes Sorensen <Jes.Sorensen@redhat.com>
> wrote:
> There is a small race in the exclusion between discard and recovery.
> This patch on top should fix it (I hope).
> Thanks for testing.
I'll give it a spin. I am running on a quad-core Xeon system:
Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz, with 8GB of RAM, and the
tests on a 3TB SATA III drive.
My loop image files are like this:
-rw-r--r--. 1 root root 268435456 Mar 12 09:53 img0
-rw-r--r--. 1 root root 268435456 Mar 12 09:53 img1
-rw-r--r--. 1 root root 268435456 Mar 12 09:53 img2
-rw-r--r--. 1 root root 268435456 Mar 12 09:26 img3
I've tried storing them both on ext4 and xfs, didn't seem to make a
difference for the test results.
Cheers,
Jes
next prev parent reply other threads:[~2013-03-13 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 13:50 raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65 Jes Sorensen
2013-03-04 21:00 ` NeilBrown
2013-03-05 8:44 ` Jes Sorensen
2013-03-06 2:18 ` NeilBrown
2013-03-06 9:31 ` Jes Sorensen
2013-03-11 22:32 ` NeilBrown
2013-03-12 1:32 ` NeilBrown
2013-03-12 11:12 ` joystick
2013-03-20 0:54 ` NeilBrown
2013-03-12 13:45 ` Jes Sorensen
2013-03-12 23:35 ` NeilBrown
2013-03-13 7:32 ` Jes Sorensen [this message]
2013-03-14 7:35 ` Jes Sorensen
2013-03-20 0:55 ` NeilBrown
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=wrfj7glb92lc.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=eguan@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@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 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.