On Thu, Aug 25, 2016 at 08:48:24PM -0600, Chris Murphy wrote: > Right, so something like GPT on /dev/sda and /dev/sdb to create sda1 > and sdb1, then mdadm -C /dev/md0 --metadata=1.0 ... /dev/sda1 > /dev/sdb1, and then create a GPT on /dev/md0. The result is /dev/md0, > /dev/sda1, and /dev/sda2 will all appear to have the same GPT on them. > > I would say that's probably a bad idea, I know some tools allow it, > but it creates an ambiguity. It could be argued to be inconsistent > with the UEFI spec. The only nesting it describes is MBR on a GPT > partition, not GPT nested in a GPT partition. This is probably also > better done using LVM. Otherwise we get nutty things... We had similar ambiguities in MBR-land, if you set the active flag on more than one partition, or if you have more than one extended partition. Since the behavior in those cases is undefined, it seems wise to avoid creating them. Better if the specification avoids these situations - that no combination of bits can create an ambiguous interpretation - but in the occasional cases where that can't be avoided you're best off not creating those situations. -- http://www.subspacefield.org/~travis/ | if spammer then john@xxxxxxxxxxxxxxxxx "Computer crime, the glamor crime of the 1970s, will become in the 1980s one of the greatest sources of preventable business loss." John M. Carroll, "Computer Security", first edition cover flap, 1977 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
