Activity log for bug #1617919

Date Who What changed Old value New value Message
2016-08-29 08:04:26 Johan Ehnberg bug added bug
2016-08-29 08:04:53 Johan Ehnberg affects gvfs (Ubuntu) mdadm (Ubuntu)
2016-09-06 09:06:14 Launchpad Janitor mdadm (Ubuntu): status New Confirmed
2016-09-22 07:38:06 Technical Contact bug added subscriber Technical Contact
2016-10-28 08:07:54 claus bug added subscriber claus
2016-12-09 16:02:40 Andrew Martin bug added subscriber Andrew Martin
2017-10-09 12:22:28 Dan Streetman bug added subscriber Dan Streetman
2017-10-09 14:41:55 Dan Streetman nominated for series Ubuntu Xenial
2017-10-09 14:50:11 Dan Streetman nominated for series Ubuntu Trusty
2017-10-09 14:58:53 Dan Streetman mdadm (Ubuntu): assignee Dan Streetman (ddstreet)
2017-10-09 14:58:56 Dan Streetman mdadm (Ubuntu): importance Undecided Low
2017-10-09 14:58:59 Dan Streetman mdadm (Ubuntu): status Confirmed In Progress
2017-10-09 15:16:12 Dan Streetman attachment added lp1617919-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+attachment/4965922/+files/lp1617919-trusty.debdiff
2017-10-09 15:16:25 Dan Streetman attachment added lp1617919-xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1617919/+attachment/4965923/+files/lp1617919-xenial.debdiff
2017-10-09 15:23:59 Dan Streetman description On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two machines. Everything works as normal though, and the RAID arrays are not degraded. [3712474.763430] mdadm[17665]: segfault at 0 ip 00007fd0369bed16 sp 00007fff8c5c9478 error 4 in libc-2.23.so[7fd036934000+1c0000] [3712474.949633] mdadm[17727]: segfault at 0 ip 00007f2814111d16 sp 00007ffca92fe168 error 4 in libc-2.23.so[7f2814087000+1c0000] [3798863.008741] mdadm[25359]: segfault at 0 ip 00007fa6af198d16 sp 00007ffc1b253e48 error 4 in libc-2.23.so[7fa6af10e000+1c0000] [3798863.190382] mdadm[25393]: segfault at 0 ip 00007f72218a0d16 sp 00007ffef918f118 error 4 in libc-2.23.so[7f7221816000+1c0000] [3885251.386711] mdadm[32081]: segfault at 0 ip 00007f3d99ca2d16 sp 00007ffe5e69a7a8 error 4 in libc-2.23.so[7f3d99c18000+1c0000] [3885251.402337] mdadm[32083]: segfault at 0 ip 00007f770ccc1d16 sp 00007ffe16074378 error 4 in libc-2.23.so[7f770cc37000+1c0000] [3971638.258574] mdadm[7936]: segfault at 0 ip 00007fcacddb3d16 sp 00007ffc062faff8 error 4 in libc-2.23.so[7fcacdd29000+1c0000] [3971638.410750] mdadm[8053]: segfault at 0 ip 00007ff573757d16 sp 00007fffd3cca398 error 4 in libc-2.23.so[7ff5736cd000+1c0000] The segfault message always appears twice in quick succession. It seems to be triggered by /etc/cron.daily/mdadm which essentially runs mdadm --monitor --scan --oneshot As such, the frequency is around every 85000 seconds or 24 hours give or take, depending on when the cron job was executed. It does not happen when running the command manually. There is one similar bug #1576055 concerning libc and a few cases elsewhere but further digging into this has yet to reveal anything conclusive. Note that these machines have almost exactly the same hardware (Xeon D-1518, 16GB ECC), so hardware design flaws cannot be ruled out. However, memory testing has not turned up any faults. That said, I know some segfaults can be difficult to find even when they are hardware issues. [impact] the mdadm cron jobs invoke mdadm to scan raid arrays periodically, but when inside a unpriviledged container mdadm does not have access to the arrays, and it segfaults when invoked. This is logged in the host system's logs, and while harmless, causes confusion about mdadm segfaults in the host logs. [test case] install a ubuntu system and create one or more raid/mdadm arrays. create a container, with either trusty or xenial inside the container. in the container, install mdadm. Run: $ mdadm --monitor --scan --oneshot that is the command run by mdadm's cronjob (though other variations on the command will also segfault). With the current mdadm code, mdadm will segfault. With the patched code, mdadm exits normally. [regression potential] this patch changes mdadm's code that processes each array's name; a bug in this area may cause mdadm to fail when performing any operation on arrays, but not during the operation, the failure would occur before mdadm opened the array. [other info] this commit fixing this is already upstream and included in zesty and later; this is required only for trusty and xenial. [original description] On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two machines. Everything works as normal though, and the RAID arrays are not degraded. [3712474.763430] mdadm[17665]: segfault at 0 ip 00007fd0369bed16 sp 00007fff8c5c9478 error 4 in libc-2.23.so[7fd036934000+1c0000] [3712474.949633] mdadm[17727]: segfault at 0 ip 00007f2814111d16 sp 00007ffca92fe168 error 4 in libc-2.23.so[7f2814087000+1c0000] [3798863.008741] mdadm[25359]: segfault at 0 ip 00007fa6af198d16 sp 00007ffc1b253e48 error 4 in libc-2.23.so[7fa6af10e000+1c0000] [3798863.190382] mdadm[25393]: segfault at 0 ip 00007f72218a0d16 sp 00007ffef918f118 error 4 in libc-2.23.so[7f7221816000+1c0000] [3885251.386711] mdadm[32081]: segfault at 0 ip 00007f3d99ca2d16 sp 00007ffe5e69a7a8 error 4 in libc-2.23.so[7f3d99c18000+1c0000] [3885251.402337] mdadm[32083]: segfault at 0 ip 00007f770ccc1d16 sp 00007ffe16074378 error 4 in libc-2.23.so[7f770cc37000+1c0000] [3971638.258574] mdadm[7936]: segfault at 0 ip 00007fcacddb3d16 sp 00007ffc062faff8 error 4 in libc-2.23.so[7fcacdd29000+1c0000] [3971638.410750] mdadm[8053]: segfault at 0 ip 00007ff573757d16 sp 00007fffd3cca398 error 4 in libc-2.23.so[7ff5736cd000+1c0000] The segfault message always appears twice in quick succession. It seems to be triggered by /etc/cron.daily/mdadm which essentially runs mdadm --monitor --scan --oneshot As such, the frequency is around every 85000 seconds or 24 hours give or take, depending on when the cron job was executed. It does not happen when running the command manually. There is one similar bug #1576055 concerning libc and a few cases elsewhere but further digging into this has yet to reveal anything conclusive. Note that these machines have almost exactly the same hardware (Xeon D-1518, 16GB ECC), so hardware design flaws cannot be ruled out. However, memory testing has not turned up any faults. That said, I know some segfaults can be difficult to find even when they are hardware issues.
2017-10-09 16:24:09 Ubuntu Foundations Team Bug Bot tags patch
2017-10-09 16:24:16 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Sponsors Team
2017-10-10 11:13:51 Dimitri John Ledkov bug task added mdadm (Ubuntu Xenial)
2017-10-10 11:13:56 Dimitri John Ledkov bug task added mdadm (Ubuntu Trusty)
2017-10-10 11:14:02 Dimitri John Ledkov mdadm (Ubuntu): assignee Dan Streetman (ddstreet)
2017-10-10 11:14:05 Dimitri John Ledkov mdadm (Ubuntu): status In Progress Fix Released
2017-10-10 11:14:08 Dimitri John Ledkov mdadm (Ubuntu Trusty): status New Triaged
2017-10-10 11:14:11 Dimitri John Ledkov mdadm (Ubuntu Xenial): status New Triaged
2017-10-10 11:14:14 Dimitri John Ledkov mdadm (Ubuntu Trusty): importance Undecided High
2017-10-10 11:14:15 Dimitri John Ledkov mdadm (Ubuntu Xenial): importance Undecided High
2017-10-10 11:14:17 Dimitri John Ledkov mdadm (Ubuntu Trusty): assignee Dimitri John Ledkov (xnox)
2017-10-10 11:14:18 Dimitri John Ledkov mdadm (Ubuntu Xenial): assignee Dimitri John Ledkov (xnox)
2017-10-23 16:35:09 Dan Streetman tags patch patch sts-sponsor-ddstreet
2017-11-03 14:38:49 Dan Streetman mdadm (Ubuntu Trusty): assignee Dimitri John Ledkov (xnox) Dan Streetman (ddstreet)
2017-11-03 14:38:52 Dan Streetman mdadm (Ubuntu Xenial): assignee Dimitri John Ledkov (xnox) Dan Streetman (ddstreet)
2017-11-03 16:23:13 Eric Desrochers bug added subscriber Eric Desrochers
2017-11-03 16:27:08 Dan Streetman mdadm (Ubuntu Trusty): status Triaged In Progress
2017-11-03 16:27:10 Dan Streetman mdadm (Ubuntu Xenial): status Triaged In Progress
2017-11-03 16:29:08 Dan Streetman bug added subscriber SRU Verification
2017-11-03 16:29:31 Dan Streetman tags patch sts-sponsor-ddstreet patch sts-sponsor-ddstreet-done
2017-11-08 13:17:01 Chris J Arges mdadm (Ubuntu Xenial): status In Progress Fix Committed
2017-11-08 13:17:04 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2017-11-08 13:17:11 Chris J Arges tags patch sts-sponsor-ddstreet-done patch sts-sponsor-ddstreet-done verification-needed verification-needed-xenial
2017-11-08 13:18:35 Chris J Arges removed subscriber Ubuntu Sponsors Team
2017-11-08 13:18:50 Chris J Arges mdadm (Ubuntu Trusty): status In Progress Fix Committed
2017-11-08 13:18:58 Chris J Arges tags patch sts-sponsor-ddstreet-done verification-needed verification-needed-xenial patch sts-sponsor-ddstreet-done verification-needed verification-needed-trusty verification-needed-xenial
2017-11-08 15:08:08 Dan Streetman tags patch sts-sponsor-ddstreet-done verification-needed verification-needed-trusty verification-needed-xenial patch sts-sponsor-ddstreet-done verification-done verification-done-trusty verification-done-xenial
2017-11-16 16:21:37 Launchpad Janitor mdadm (Ubuntu Trusty): status Fix Committed Fix Released
2017-11-16 16:21:40 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2017-11-16 16:22:29 Launchpad Janitor mdadm (Ubuntu Xenial): status Fix Committed Fix Released