On Wed, Sep 9, 2009 at 5:08 PM, Giuseppe Iuculano <[email protected]> wrote: > well, so probably we need another boot option to "force" dmraid -Z also if > root > partition is not in a dmraid array. Removing that code will help live cd > users, > but doesn't fix the original issue. > The nodmraid option is useful for debugging, but when you use that, your > dmraid > array will not be activated.
dmraid-activate is used by udev when discovering devices. At this level it should not make any assumptions or guesswork to what the device is going to used for later (root or not). I definitely think we should treat all raid arrays consistently. What is the original issue about? Lior has a fakeraid array (per definition, until he removes the fakeraid signatures from the partition), but he does not want to use dmraid. Well, he can then use "nodmraid" or remove dmraid to pretend he has no fakeraid (*). This is a "won't fix" for us. If an operating system has fakeraid support it should activate all the fakeraids it detects. If you have configured your disks in your BIOS to be fakeraid arrays, it would be wrong to not treat them as such. And when activating an array, it makes perfectly sense to hide the "partitions" on the raid members. As pointed out by others, these are not real partitions, just underlying data to the fakeraid array which happens to appear as a real partition because the members are simply mirrored (if any other RAID configuration than simple mirroring is used, this will be even more obvious). We should not try to support broken configurations where for instance the user wants to activate the array but still wants direct access to parts of the underlying raid members. *) If he has another fakeraid array which he does want to activate, he can do that manually with dmraid commands. His setup is broken, but he can still use it, on his own. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
