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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617919 Title: mdadm segfault error 4 in libc-2.23.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
