Good catch. A possible workaround would be to patch dmraid to wait a
second and retry a few times before giving up. I think a more proper
long term solution is that dmraid should not be used to remove the
partitions from the disk when activated, but rather the partitions
should not be created in the first place. This means removing the
partition table parsing from the kernel and letting udev handle it with
partx, which should be smart enough to notice the disk is a raid member
and skip processing it. This isn't likely to happen any time soon
though.
** Changed in: dmraid (Ubuntu)
Status: New => Confirmed
--
race condition leaves raid raw devices exposed
https://bugs.launchpad.net/bugs/362768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
