Comment 38 for bug 38409
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #38 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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.