Comment 8 for bug 1054948

Revision history for this message
JK (j-c-k) wrote :

But wouldn't that simply only imply that dmraid and mdadm are not supposed to co-exist? I'm a bit puzzled about this change. As far as I understand this, the auto-assemble rules have been removed just to guarantee the function of dmraid - temporarily or not.
Automated installation procedure aside, it is currently not possible to remove dmraid and add mdadm to get an imsm 1.3 (external metadata) running out of the box, right? If no dmraid is present, the cut-down of mdadm does not seem necessary.

It seems this can also be user-fixed without jumping through many hoops by restoring previous rules, right?

From my perspective it then boils down to the problem that, even if auto-assembly would be enabled, mdadm currently does not support the root being member of the array itself. As I mentioned in 1028677, mdmon is missing in the initrd which prohibts the any assembly at that point. The effect is that mdadm sets of read-only devices, instead of auto-read-only. With adding mdmon this boots but during shutdown the array seems to be taken down too early so the system does not finish that gracefully. There have been attempts to fix this in debian (1054773). See also [1].

[1] http://www.spinics.net/lists/raid/msg37335.html