Your message dated Thu, 18 Jan 2007 00:03:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403687: lvm2: several issues with devmapper devices
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: lvm2
Version: 2.02.06-3
Severity: serious
There are currently at least two reports floating around that seem to have
the same root cause: the way devmapper devices are created for lvm
partitions. The relevant reports are:
http://bugs.debian.org/401393 (currently against lilo)
http://bugs.debian.org/402511 (currently against lvm-common)
These recent issues seem to have been triggered by a recent change in udev
on request of the Gnome team:
http://bugs.debian.org/392623
Although this is a lot older, it seems related:
http://bugs.debian.org/343671
Similar issues are also seen in other distributions:
https://bugzilla.novell.com/show_bug.cgi?id=178321
which has a possible patch in comment 28:
https://bugzilla.novell.com/attachment.cgi?id=102957
IMO the issues listed above together are serious enough that they should
be fixed, or at least addressed, before the release of Etch.
I'm filing the BR against lvm2 as that is the package most responsible for
the lvm setup in Debian, though fixing this probably involves udev as
well.
IMO 401393 and 402511 are serious enough that reverting the change from
392623 should be considered as one option.
Cheers,
FJP
pgpLlrXlTACy9.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
The main intention of this BR was to get some clarity in the regressions
seen because of the change in udev.
Further analysis in http://bugs.debian.org/406697 has now shown that the
reason the /dev/dm-* devices are not removed, is the fact that udevd has
already been killed by the time the crypto and lvm scripts are run on
shutdown and thus the events created by the kernel are no longer
processed as they would be if the system was running normally.
This makes the issue a lot less structural than initially feared (at least
by me) and thus this "umbrella" bug report can be safely closed.
Cheers,
FJP
pgpApf0h1fes1.pgp
Description: PGP signature
--- End Message ---
