Neil Brown wrote:
>On Wednesday November 20, sdake@mvista.com wrote:
>
>
>>Neil,
>>
>>I would suggest adding a 64 bit field called "unique_identifier" to the
>>per-device structure. This would allow a RAID volume to be locked to a
>>specific host, allowing the ability for true multihost operation.
>>
>>
>
>You seem to want a uniq id in 'per device' which will identify the
>'volume'.
>That doesn't make sense to me so maybe I am missing something.
>If you want to identify the 'volume', you put some sort of id in the
>'per-volume' data structure.
>
>This is what the 'name' field is for.
>
>
This is useful, atleast in the current raid implementation, because
md_import can be changed to return an error if the device's unique
identifier doesn't match the host identifier. In this way, each device
of a RAID volume is individually locked to the specific host, and
rejection occurs at import of the device time.
Perhaps locking using the name field would work except that other
userspace applications may reuse that name field for some other purpose,
not providing any kind of uniqueness.
Thanks for the explination of how the name field was intended to be used.
-steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:34 EST