That debian bug is actually unrelated. It is about a set of disks that
already is being used as part of a dmraid array and the person also
wanted to use them as part of an mdadm array, which is an invalid
configuration. In your case, you have an array that is using a format
that is now recognized by both mdadm and dmraid. The easiest solution
is not to use the ddf format and use mdadm's native format instead.
Long term, the ddf support in dmraid should probably be disabled and
just let mdadm handle it.
** Project changed: dmraid => null
** Changed in: null
Importance: Unknown => Undecided
** Changed in: null
Status: Unknown => New
** Changed in: null
Remote watch: Debian Bug tracker #534274 => None
** Changed in: null
Status: New => Invalid
** Changed in: udev
Status: New => Invalid
** Changed in: dmraid (Ubuntu)
Importance: Undecided => Medium
** Changed in: dmraid (Ubuntu)
Status: New => Triaged
** Summary changed:
- dmraid interferes with mdadm
+ ddf1 format should be disabled in dmraid in favor of mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
ddf1 format should be disabled in dmraid in favor of mdadm
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
