[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-16 Thread Launchpad Bug Tracker
This bug was fixed in the package mdadm - 3.3-2ubuntu7.6 --- mdadm (3.3-2ubuntu7.6) xenial; urgency=medium * Prevent segfault when get_md_name() returns NULL This fixes mdadm segfaults when running inside a container. (LP: #1617919) -- Dan Streetman

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-16 Thread Launchpad Bug Tracker
This bug was fixed in the package mdadm - 3.2.5-5ubuntu4.4 --- mdadm (3.2.5-5ubuntu4.4) trusty; urgency=medium * Prevent segfault when get_md_name() returns NULL This fixes mdadm segfaults when running inside a container. (LP: #1617919) -- Dan Streetman

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-08 Thread Dan Streetman
>From inside xenial container, with raid array in host: ubuntu@mdadm:~$ dpkg -l | grep mdadm ii mdadm3.3-2ubuntu7.5 amd64tool to administer Linux MD arrays (software RAID) ubuntu@mdadm:~$ mdadm --monitor --scan -1 Segmentation

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-08 Thread Chris J Arges
Hello Johan, or anyone else affected, Accepted mdadm into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-03 Thread Dan Streetman
** Changed in: mdadm (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: mdadm (Ubuntu Xenial) Status: Triaged => In Progress ** Tags removed: sts-sponsor-ddstreet ** Tags added: sts-sponsor-ddstreet-done -- You received this bug notification because you are a member of

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-11-03 Thread Dan Streetman
** Changed in: mdadm (Ubuntu Trusty) Assignee: Dimitri John Ledkov (xnox) => Dan Streetman (ddstreet) ** Changed in: mdadm (Ubuntu Xenial) Assignee: Dimitri John Ledkov (xnox) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-23 Thread Dan Streetman
** Tags added: sts-sponsor-ddstreet -- 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:

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-10 Thread Dimitri John Ledkov
** Also affects: mdadm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mdadm (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: mdadm (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: mdadm (Ubuntu)

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Ubuntu Foundations Team Bug Bot
The attachment "lp1617919-trusty.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag,

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
verified the patch fixes this on xenial and trusty using test ppa from comment 8 -- 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

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
this is fixed upstream already by commit https://github.com/neilbrown/mdadm/commit/1e08717f0b7856b389e9d5eb2dc330d146636183 that commit is included in zesty and later, this is needed only for trusty and xenial ** Description changed: - On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
test ppa with fixed mdadm: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1617919 -- 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

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
** Patch added: "lp1617919-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+attachment/4965923/+files/lp1617919-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
** Patch added: "lp1617919-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+attachment/4965922/+files/lp1617919-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2017-10-09 Thread Dan Streetman
** Changed in: mdadm (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: mdadm (Ubuntu) Importance: Undecided => Low ** Changed in: mdadm (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-11-03 Thread claus
I just got the following feedback from Stéphane Graber (LXC and LXD project leader): "It's not a bug for it to be installed as the Ubuntu image we run is bit for bit identical to what's run on the cloud or on physical servers and that's on purpose. mdadm is supposed to be configured in a way

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-11-03 Thread Johan Ehnberg
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

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-11-03 Thread claus
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

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-10-28 Thread claus
This morning I had that message for the first time (server is up with this package setup for several days now): Oct 28 08:25:01 apphost1 kernel: [331502.883078] mdadm[19974]: segfault at 0 ip 7f99f55d4d16 sp 75dbc7d8 error 4 in libc-2.23.so[7f99f554a000+1c] Versions of packages

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-10-24 Thread Andrew Martin
I'm still seeing this on 4.4.0-38-generic and the same versions of libc and mdadm that you listed in comment 2 -- 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

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-09-06 Thread Johan Ehnberg
With the latest updates and a reboot and a few days of uptime, the message has not yet reappeared. This may have been fixed? linux-image 4.4.0-36-generic libc 2.23-0ubuntu3 mdadm 3.3-2ubuntu7.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1617919] Re: mdadm segfault error 4 in libc-2.23.so

2016-09-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mdadm (Ubuntu) Status: New => Confirmed -- 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: