From: Phillip Susi <psusi@ubuntu.com>
To: "Tomczak, Marcin" <marcin.tomczak@intel.com>
Cc: "neilb@suse.de" <neilb@suse.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Patelczyk, Maciej" <maciej.patelczyk@intel.com>,
"Dorau, Lukasz" <lukasz.dorau@intel.com>
Subject: Re: [PATCH] imsm: Forbid spanning between multiple controllers.
Date: Mon, 14 Jan 2013 09:45:06 -0500 [thread overview]
Message-ID: <50F419F2.9050809@ubuntu.com> (raw)
In-Reply-To: <8565BDA60DEA9E4C91B1047AD1958FBE1DEC8F5B@IRSMSX104.ger.corp.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/14/2013 8:02 AM, Tomczak, Marcin wrote:
> Hi. Yes, mdadm will refuse any commands, when you try to use disks
> attached to multiple controllers. Also mdadm supports IMSM metadata
> only if you have a machine with Intel OROM (and the patch "Forbid
> spanning" changes nothing about it).
Why is this? One of the nice things about dmraid was that since it
really was just software raid, if your controller blew you could
recover your data by moving the drives to another machine and still
recognize them. Why should mdadm care about the controller?
I suppose it is nice to warn people that they are trying to create an
array that the bios won't recognize, but mdadm should not refuse to
run an array just because some hardware that is completely unnecessary
is not found.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ9BnyAAoJEJrBOlT6nu75tikH/jQAsx4waselA6rrKC8aFD7+
oG5pphTskS10iukkJGX8d+o/HiiMM66IuMqM3vRSNZO40P6arhAETE02jvNY9vFN
fI61AMpCv0FvBFv83RRmh19HkHLQEgiztcLRI7GeTNl5aOnC4wk8NY/Rqt022bhV
MGHickXUDNXtoWSXE3x03aXm9cwjIwfPbDrt3jOyrf9EqgZZW2j8uqY3PbH5Zcav
slKjFOaVt98nvLeDLpBJ6pR4vKq3Qax+pOPNdvlGG0GAqftH/iEYHsopmM4D4o5L
21cI1CRfmyaF8ro0ryZPJkQVe46Ya41Qb1wd9Y6pg5mfbqGiwbQvMHi7o53Mc70=
=NumJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-14 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 14:46 [PATCH] imsm: Forbid spanning between multiple controllers Marcin Tomczak
2012-11-19 0:08 ` NeilBrown
2013-01-10 21:57 ` Phillip Susi
[not found] ` <8565BDA60DEA9E4C91B1047AD1958FBE1DEC8F5B@IRSMSX104.ger.corp.intel.com>
2013-01-14 14:45 ` Phillip Susi [this message]
2013-01-15 10:31 ` Patelczyk, Maciej
2013-01-15 14:57 ` Phillip Susi
2013-01-16 8:49 ` John Robinson
2013-01-16 9:58 ` Patelczyk, Maciej
2013-01-16 10:01 ` Patelczyk, Maciej
2013-01-16 14:26 ` Phillip Susi
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=50F419F2.9050809@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=maciej.patelczyk@intel.com \
--cc=marcin.tomczak@intel.com \
--cc=neilb@suse.de \
/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.