On Wed, Nov 20, 2002 at 03:09:18PM +1100, Neil Brown wrote:
> The interpretation of the 'name' field would be up to the user-space
> tools and the system administrator.
> I imagine having something like:
> host:name
> where if "host" isn't the current host name, auto-assembly is not
> tried, and if "host" is the current host name then:
> if "name" looks like "md[0-9]*" then the array is assembled as that
> device
> else the array is assembled as /dev/mdN for some large, unused N,
> and a symlink is created from /dev/md/name to /dev/mdN
> If the "host" part is empty or non-existant, then the array would be
> assembled no-matter what the hostname is. This would be important
> e.g. for assembling the device that stores the root filesystem, as we
> may not know the host name until after the root filesystem were loaded.
Hmm, what is the intended future interaction of DM and MD? Two
ways at the same problem? Just curious.
Assuming MD as a continually used feature, the "name" bits above
seem to be preparing to support multiple shared users of the array. If
that is the case, shouldn't the superblock contain everything needed for
"clustered" operation?
Joel
--"When I am working on a problem I never think about beauty. I only think about how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." - Buckminster Fuller
Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: joel.becker@oracle.com Phone: (650) 506-8127 - 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:32 EST