Comment 6 for bug 1617919

Johan Ehnberg (johan-ehnberg) wrote :

Yes this makes a lot of sense. The situation is the same for me, but I started automatically removing a list of packages from my lxd containers - including mdadm. That's why the problem disappeared.

Mdadm could still make sense in a container (privileged with raw access to devices etc.) but considering what containers are typically used for that should be quite rare. So at least as a workaround when mdadm is not needed, removing mdadm is an option.

So we have confirmed this. Is anyone on linux-raid? Lxd devs may also be interested.