From: Chris Webb <chris@arachsys.com>
To: Ferenc Wagner <wferi@niif.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: harmful parallel AoE check/resync
Date: Mon, 6 Apr 2009 17:39:18 +0100 [thread overview]
Message-ID: <20090406163918.GC17707@arachsys.com> (raw)
In-Reply-To: <87ljqdvopc.fsf@tac.ki.iif.hu>
Ferenc Wagner <wferi@niif.hu> writes:
> md_do_sync() in md.c takes care not to resync/check MD devices built
> on different parts of the same physical device in parallel. This does
> not account for AoE devices, which, however, most of the time share
> and are limited by network bandwidth.
...and may also share underlying backing devices at the far end.
I run a cluster with a lot of cross-access of storage via AoE, combined
using md. In fact, every RAID device on every host shares physical devices
behind AoE, so I crack this particular nut locally with the following
sledge-hammer:
diff --git a/drivers/md/md.c b/drivers/md/md.c
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -5744,8 +5744,7 @@
if (mddev2 == mddev)
continue;
if (!mddev->parallel_resync
- && mddev2->curr_resync
- && match_mddev_units(mddev, mddev2)) {
+ && mddev2->curr_resync) {
DEFINE_WAIT(wq);
if (mddev < mddev2 && mddev->curr_resync == 2) {
/* arbitrarily yield */
This clearly isn't the right solution more generally, though, and it'd be
great to have a more elegant way of defining which backing devices conflict
with one another, and which are independent.
Cheers,
Chris.
prev parent reply other threads:[~2009-04-06 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 14:31 harmful parallel AoE check/resync Ferenc Wagner
2009-04-06 16:39 ` Chris Webb [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=20090406163918.GC17707@arachsys.com \
--to=chris@arachsys.com \
--cc=linux-raid@vger.kernel.org \
--cc=wferi@niif.hu \
/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).