From: Neil Brown <neilb@cse.unsw.edu.au>
To: Jasper Spaans <jasper@spaans.ds9a.nl>,
Linus Torvalds <torvalds@transmeta.com>
Cc: George Garvey <tmwg-linuxknl@inxservices.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
MOLNAR Ingo <mingo@chiara.elte.hu>
Subject: [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
Date: Mon, 20 Nov 2000 11:49:03 +1100 (EST) [thread overview]
Message-ID: <14872.29951.707116.16506@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Jasper Spaans on Sunday November 19
In-Reply-To: <20001119033943.C935@inxservices.com> <20001119140809.A21693@spaans.ds9a.nl>
Linus, Ingo:
the attached patch, modifies a warning message in md.c which seems to
often cause confusion - the following email includes one example
there-of (there have been others over the months).
Hopefully the new text is clearer.
(patch against 2.4.0-test11-pre7)
NeilBrown
On Sunday November 19, jasper@spaans.ds9a.nl wrote:
> On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
> > Is this something to be concerned about? It sounds like a disaster waiting
> > to happen from the message. This is on 2 systems (with similar disk setups
> > [same other than size]).
>
> > Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical units with md2!
>
> Nope, nothing to worry about -- it's just a bad choice of wording ;)
>
> What it means is that some partititions in md1 and md2 are on the same disk,
> and that the md-code will not do the reconstruction of these arrays in
> parallel [of course, for performance reasons].
>
--- ./drivers/md/md.c 2000/11/20 00:33:08 1.2
+++ ./drivers/md/md.c 2000/11/20 00:44:19 1.3
@@ -3279,7 +3279,7 @@
if (mddev2 == mddev)
continue;
if (mddev2->curr_resync && match_mddev_units(mddev,mddev2)) {
- printk(KERN_INFO "md: serializing resync, md%d has overlapping physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
+ printk(KERN_INFO "md: serializing resync, md%d has shares one or more physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
serialize = 1;
break;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-20 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-19 11:39 What is 2.4.0-test10: md1 has overlapping physical units with md2! George Garvey
2000-11-19 12:51 ` Matti Aarnio
2000-11-19 13:08 ` Jasper Spaans
2000-11-20 0:49 ` Neil Brown [this message]
2000-11-20 12:25 ` [PATCH] " Ingo Molnar
2000-11-20 17:15 ` [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical unitswith md2! Marc Mutz
2000-11-20 14:41 ` [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical units with md2! Ruth Ivimey-Cook
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=14872.29951.707116.16506@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=jasper@spaans.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@chiara.elte.hu \
--cc=tmwg-linuxknl@inxservices.com \
--cc=torvalds@transmeta.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).