From: Jasper Spaans <jasper@spaans.ds9a.nl>
To: George Garvey <tmwg-linuxknl@inxservices.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
Date: Sun, 19 Nov 2000 14:08:09 +0100 [thread overview]
Message-ID: <20001119140809.A21693@spaans.ds9a.nl> (raw)
In-Reply-To: <20001119033943.C935@inxservices.com>
In-Reply-To: <20001119033943.C935@inxservices.com>; from tmwg-linuxknl@inxservices.com on Sun, Nov 19, 2000 at 03:39:43AM -0800
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].
Regards,
--
Jasper Spaans <jasper@spaans.ds9a.nl>
-
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-19 13:41 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 [this message]
2000-11-20 0:49 ` [PATCH] " Neil Brown
2000-11-20 12:25 ` 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=20001119140809.A21693@spaans.ds9a.nl \
--to=jasper@spaans.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tmwg-linuxknl@inxservices.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