Doug Ledford wrote:
quoted text
> On 04/28/2010 02:34 PM, Labun, Marcin wrote:
>> Should an array be split (not assembled) if a domain paths are dividing array into two separate DOMAIN?
> 
> I don't think so.  Amongst other things, this would make it possible to
> render a machine unbootable if you had a type in a domain path.  I think
> I would prefer to allow established arrays to assemble regardless of
> domain path entries.

This is what I was calling the 'enforce=' policy in previous mails. 
Whether to block, warn, or ignore arrays that span a domain.  I can see 
someone wanting to have something like enforce=platform to make sure we 
Linux tries to assemble an array that the option-rom can't put together.

quoted text
>>>  I'm happy to rework the code to support it if there's a valid use
>>> case, but so far my design goal has been to have a path only appear in
>>> one domain, and to then perform the appropriate action based upon that
>>> domain.
>> What is then the purpose of metadata keyword?
> 
> Mainly as a hint that a given domain uses a specific type of metadata.

Yeah, to protect against cases where a stale disk is plugged into an 
unexpected port.

--
Dan

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html