Linux RAID subsystem development
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Phillip Susi <psusi@ubuntu.com>
Cc: "Patelczyk, Maciej" <maciej.patelczyk@intel.com>,
	"Tomczak, Marcin" <marcin.tomczak@intel.com>,
	"neilb@suse.de" <neilb@suse.de>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Dorau, Lukasz" <lukasz.dorau@intel.com>
Subject: Re: [PATCH] imsm: Forbid spanning between multiple controllers.
Date: Wed, 16 Jan 2013 08:49:22 +0000	[thread overview]
Message-ID: <50F66992.7090400@anonymous.org.uk> (raw)
In-Reply-To: <50F56E52.1090302@ubuntu.com>

On 15/01/2013 14:57, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 1/15/2013 5:31 AM, Patelczyk, Maciej wrote:
>> Hi Phillip,
>>
>> Mdadm does not care about the controller unless you created IMSM
>> based RAID. Basically you can create that type of RAID *only* on
>> Intel based platforms with OROM enabled. It's Intel solution, we
>> support it and we maintain it. It's very specific type of metadata.
[...]
>
> Warnings about potentially troublesome situations are good, but
> outright refusal is not.  Yes, I realize it would be a problem for
> Windows due to the poor way the driver has to be implemented ( why
> can't the OROM see other disks on other controllers? ), but sometimes
> you don't care about that.  For instance, if you are setting up the
> array on one machine where you can not connect all of the drives to
> the same controller ( and do not care about booting from the array on
> this machine ), but you are planning on moving them to a machine where
> they will be.  This is just one example of many situations where you
> need to be able to say "I know what I'm doing, go ahead anyway".

Isn't there, or wasn't there, an environment variable for mdadm called 
something like IMSM_PLATFORM_IGNORE for precisely this scenario? Is that 
what this patch series disabled?

Cheers,

John.


  reply	other threads:[~2013-01-16  8:49 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
2013-01-15 10:31       ` Patelczyk, Maciej
2013-01-15 14:57         ` Phillip Susi
2013-01-16  8:49           ` John Robinson [this message]
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=50F66992.7090400@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --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 \
    --cc=psusi@ubuntu.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