The problem is that dmraid needs to claim the entire disk, and disallow all other access to it. In the case of a raid1, you potentially will see 3 volumes with the same data: the two underlying mirrors and the mirror dm device. Any access to the underlying disks will be a problem. In the case of a raid0, often the kernel will see the partition table and create the devices for each partition, but they are not valid and must not be accessed.
Bear in mind that dmraid rules activate on the raw disk device, not the partitions. Something then needs to be done to prevent udev from doing anything at all with the partition devices on the disk that dmraid has claimed. -- UUID's not correctly allocated for DMRAID devices in Gutsy https://bugs.launchpad.net/bugs/154834 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
