Ok, I think I made some progress tracking this thing down: On the host, where I experienced the bug, I have an LXD/LXC container running. It turns out that mdadm is installed by default inside a container created by "lxc launch ubunut:16.04 c1" And when I call /etc/cron.daily/mdadm inside the container I get the segfault which is also logged in the host system. So I think there are two bugs here: a) mdadm should not segfault b) mdadm should not be in the container by default (makes no sense, right?) For this part I think a separate bug should be filed somewhere, but I have no clue where this should be put?
-- 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
