Activity log for bug #38409

Date Who What changed Old value New value Message
2006-04-06 13:11:45 Reinhard Tartler bug added bug
2006-04-06 13:12:23 Reinhard Tartler bug added subscriber Fabio Massimo Di Nitto
2006-04-14 20:08:35 Reinhard Tartler bug assigned to Debian
2006-04-26 10:42:25 Reinhard Tartler lvm2: status Unconfirmed Confirmed
2006-04-26 10:42:25 Reinhard Tartler lvm2: severity Normal Major
2006-04-26 10:42:25 Reinhard Tartler lvm2: statusexplanation Maybe we should set the milestone to 6.06 as well?
2006-04-28 14:43:14 Scott James Remnant (Canonical) lvm2: status Confirmed Fix Released
2006-04-28 14:43:14 Scott James Remnant (Canonical) lvm2: statusexplanation Maybe we should set the milestone to 6.06 as well? New udev uploaded.
2006-04-28 18:46:23 Fabio Massimo Di Nitto lvm2: status Fix Released Confirmed
2006-04-28 18:46:23 Fabio Massimo Di Nitto lvm2: statusexplanation New udev uploaded. Scott thanks for uploading the workaround. I want to keep this bug open for reference until we have a real fix. Fabio
2006-05-03 21:27:30 Matt Zimmerman lvm2: severity Major Normal
2006-05-03 21:27:30 Matt Zimmerman lvm2: statusexplanation Scott thanks for uploading the workaround. I want to keep this bug open for reference until we have a real fix. Fabio This change alleviates the problem; reducing severity to normal. udev (079-0ubuntu28) dapper; urgency=low * Ignore device-mapper devices and let LVM take care of creating them. -- Scott James Remnant <scott@ubuntu.com> Fri, 28 Apr 2006 15:42:37 +0100
2007-01-27 16:04:10 Reinhard Tartler lvm2: importance Medium Critical
2007-01-27 16:04:10 Reinhard Tartler lvm2: statusexplanation This change alleviates the problem; reducing severity to normal. udev (079-0ubuntu28) dapper; urgency=low * Ignore device-mapper devices and let LVM take care of creating them. -- Scott James Remnant <scott@ubuntu.com> Fri, 28 Apr 2006 15:42:37 +0100 the change which alleviated the problem was reverted, which causes this bug to reappear. for feisty we look for the actual bug, so raising severity again
2007-01-27 16:04:53 Reinhard Tartler lvm2: importance Critical High
2007-01-27 16:04:53 Reinhard Tartler lvm2: statusexplanation the change which alleviated the problem was reverted, which causes this bug to reappear. for feisty we look for the actual bug, so raising severity again fabionne asked me to not set this to critical, since the proper fix was about to land.
2007-03-15 14:18:00 Reinhard Tartler lvm2: statusexplanation fabionne asked me to not set this to critical, since the proper fix was about to land. targetting for beta. fabbione told me ages ago that a fix was in a pipe, the workaround for edgy has been removed and the impact is quite severe.
2007-03-27 14:06:13 Tollef Fog Heen lvm2: statusexplanation targetting for beta. fabbione told me ages ago that a fix was in a pipe, the workaround for edgy has been removed and the impact is quite severe. Moving milestone forward
2007-03-30 10:01:36 Ian Jackson lvm2: assignee ijackson
2007-03-30 10:01:36 Ian Jackson lvm2: statusexplanation Moving milestone forward
2007-03-30 16:34:16 Scott James Remnant (Canonical) lvm2: status Confirmed In Progress
2007-03-30 16:34:16 Scott James Remnant (Canonical) lvm2: assignee ijackson keybuk
2007-03-30 16:34:16 Scott James Remnant (Canonical) lvm2: statusexplanation Packages for testing are available here: http://people.ubuntu.com/~scott/packages Please build all of the sources, and install the binaries from them. This should hopefully correct the problem.
2007-04-02 17:55:42 Scott James Remnant (Canonical) lvm2: status In Progress Fix Released
2007-04-02 17:55:42 Scott James Remnant (Canonical) lvm2: statusexplanation Packages for testing are available here: http://people.ubuntu.com/~scott/packages Please build all of the sources, and install the binaries from them. This should hopefully correct the problem. 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. In particular, due to a typo, both udev and devicemapper were attempting to create the /dev/mapper device node. This has been corrected so that only udev does this, and devicemapper waits, as was originally intended. 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.
2009-12-09 11:45:28 Launchpad Janitor branch linked lp:ubuntu/devmapper
2015-08-14 01:38:01 Bug Watch Updater debian: status New Fix Released