Activity log for bug #75681

Date Who What changed Old value New value Message
2006-12-13 23:41:01 Kees Cook bug added bug
2006-12-14 00:34:23 Kees Cook title scripts/local-top/mdadm not being called? race condition between sata and md
2006-12-14 01:02:36 Kees Cook initramfs-tools: statusexplanation
2006-12-14 01:30:09 Kees Cook title race condition between sata and md initramfs script: race condition between sata and md
2006-12-14 01:31:53 Kees Cook bug added attachment 'mdadm-race.patch' (wait for devices)
2006-12-22 22:05:51 Reinhard Tartler mdadm: status Unconfirmed Confirmed
2006-12-22 22:05:51 Reinhard Tartler mdadm: importance Undecided High
2006-12-22 22:05:51 Reinhard Tartler mdadm: statusexplanation I can confirm this bug, ajmitch is suffering as well from this.
2007-02-10 15:32:44 Reinhard Tartler bug added subscriber Scott James Remnant
2007-02-10 15:33:13 Reinhard Tartler bug added subscriber Ian Jackson
2007-02-10 15:36:00 Reinhard Tartler bug assigned to lvm2 (Ubuntu)
2007-02-12 18:17:11 Ian Jackson mdadm: status Confirmed Fix Committed
2007-02-12 18:17:11 Ian Jackson mdadm: assignee ijackson
2007-02-12 18:17:11 Ian Jackson mdadm: statusexplanation I can confirm this bug, ajmitch is suffering as well from this. I think I have fixed this in mdadm_2.5.6-7ubuntu4. Please could you install this, which I have just uploaded, and check if it works.
2007-02-16 10:14:31 Reinhard Tartler mdadm: status Fix Committed Confirmed
2007-02-16 10:14:31 Reinhard Tartler mdadm: statusexplanation I think I have fixed this in mdadm_2.5.6-7ubuntu4. Please could you install this, which I have just uploaded, and check if it works. Ian Jackson <iwj@ubuntu.com> writes: > Could you please boot with break=premount, and do this: > udevd --verbose >/tmp/udev-output 2>&1 & > udevtrigger > At this point I think you will find that your mds and lvms > are not activated properly; check with > cat /proc/partitions The thing is that I cannot reproduce the problem this way, because my raid and lvm devices come up as expected. The visible difference is, that I get tons of output on the screen after having typed udevtrigger. I suspect that they slow down udev's operation which avoids the race condition. Is there some way to avoid this massive output on the console while preserving the debug info on the tempfile?
2007-02-16 19:26:03 Kees Cook title initramfs script: race condition between sata and md boot-time race condition initializing md
2007-03-08 18:35:26 octothorp bug assigned to udev (Ubuntu)
2007-03-13 08:56:27 Reinhard Tartler mdadm: statusexplanation
2007-03-28 06:58:48 Aurelien Naldi bug added attachment 'udevd.out' (output of udevd --verbose)
2007-03-29 18:01:46 Aurelien Naldi bug added attachment 'aurelien_mdadmrace_logs.tgz' (some log files)
2007-03-29 19:18:33 Reinhard Tartler bug added attachment 'udev-output' (Udev debug log)
2007-04-02 17:51:46 Scott James Remnant (Canonical) lvm2: status Unconfirmed Fix Released
2007-04-02 17:51:46 Scott James Remnant (Canonical) lvm2: statusexplanation We believe that this problem has been corrected by a series of uploads today. Please update to ensure you have the following package versions: dmsetup, libdevmapper1.02 - 1.02.08-1ubuntu6 lvm-common - 1.5.20ubuntu12 lvm2 - 2.02.06-2ubuntu9 mdadm - 2.5.6-7ubuntu5 (not applicable unless you're also using mdadm) udev, volumeid, libvolume-id0 - 108-0ubuntu1 The problem was caused by a number of ordering issues and race conditions relating to when lvm and mdadm were called, and how those interacted to ensure the devices were created and their contents examined. This should work as follows: * an underlying block device, sda1, is detected * udev (through vol_id) detects that this is a RAID member * udev invokes mdadm, which fails to assemble because the RAID-1 is not complete * the creation of a new raid, md0, is detected * udev fails to detect this device, because it is not yet complete meanwhile: * a second underlying block device, sdb1, is detected * udev (through vol_id) detects that this is a RAID member * udev invokes mdadm, which can now complete since the set is ready * the change of the raid array, md0, is detected * udev (through vol_id) detects that this is an LVM physical volume * lvm is called to handle the creation of the devmapper devices then * various devmapper devices are detected * the devices are created by udev, named correctly under /dev/mapper * meanwhile the requesting application spins until the device exists, at which point it carries on * udev (through vol_id) detects that these devices contain typical filesystems * using vol_id it obtains the LABEL and UUID, which is used to populate /dev/disk Note that this event-based sequence is substantially different from Debian, so any bugs filed there will not be relevant to helping solve problems in Ubuntu. This should now work correctly. If it does not, I would ask that you do not re-open this bug, and instead file a new bug on lvm2 for your exact problem, even if someone else has already filed one, with verbose details about your setup and how you cause the error.
2007-04-02 17:51:57 Scott James Remnant (Canonical) mdadm: status Confirmed Fix Released
2007-04-02 17:52:05 Scott James Remnant (Canonical) udev: status Unconfirmed Fix Released
2007-04-02 17:52:05 Scott James Remnant (Canonical) udev: statusexplanation This is very much udev's fault. A fix is reportedly in debian's 105-2 version.
2007-07-30 11:06:41 Reinhard Tartler bug assigned to initramfs-tools (Ubuntu)
2007-07-30 11:07:17 Reinhard Tartler initramfs-tools: status New Incomplete
2007-07-30 11:07:17 Reinhard Tartler initramfs-tools: importance Undecided High
2007-07-30 11:07:17 Reinhard Tartler initramfs-tools: statusexplanation
2007-08-18 06:47:55 Peter Haight bug added attachment 'failed-raid.patch' (A patch to handle the case where there is a failed RAID drive.)
2009-05-24 19:30:40 xteejx initramfs-tools (Ubuntu): status New Invalid
2009-12-09 11:45:28 Launchpad Janitor branch linked lp:ubuntu/devmapper
2012-02-23 21:53:52 Kai Kasurinen removed subscriber Kai Kasurinen