Thanks, that's looks like the same data offered by two different kernel devices.
The fix will probably prevent the wrong detection, because the striping of
volumes
make the data we check for unreachable by the scsi device. But there might still
be setups where we can get exactly the same data from both devices.
We need to bump the symlink priority of dmraid symlinks. Let's see what:
ls -l /dev/.udev/names/*B080F3DA80F3A54E*
prints?
Are there the two devices competing about the same name? Then we need to
add something like: ENV{DM_UUID}=="dmraid-*", OPTIONS="link_priority=50"
to the device-mapper rules.
--
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
