Comment 10 for bug 57860

Matt Zimmerman wrote:
> The lvm script shouldn't do any waiting; that step should be in common code
> for all root device types. That way, all activation takes place, then a
> single wait for the device to appear.
>

It did not wait in dapper, but it does in edgy. Fabio said this was
because sometimes the underlying hardware was not detected at the time
the script was run, so it keeps trying to activate the volume until it
succeeds ( or 3 minutes elapses ) hoping that the devices will show up
and it will be able to activate the volume.

> And as I said above, this should be reported as a bug. Positive.
>

What exactly is the malfunction, and what should it be doing instead?
And would it be fixed in edgy? Based on my talk with Fabio on IRC, the
wait is not a malfunction but is required in order to activate the LVM
volume on slowly detected hardware. That the lvm script assumes you are
dealing with an lvm volume if the boot path starts with /dev/mapper
might be a defect, but Fabio and I could not see a workaround.

> We have a procedure for post-release updates.

It did not seem to me that this would classify as a post-release update
candidate since it is not security related, and only causes an annoying
delay in conjunction with a rare use case of a package from Universe.

If you feel this can and should be fixed in edgy, please go ahead and
file the bug against lvm, otherwise it should be resolved during the
udev rework in this development cycle.