devmapper (2:1.02.18-1ubuntu6) gutsy; urgency=low
* Don't run vol_id on devices with empty tables.
* But do run vol_id on devices with tables containing snapshot or
snapshot-origin entries, since these are the final result, not the
transient pieces.
* Also run vol_id on read-only dev
I see the latest dmsetup has fixed this in a different way.
It always creates the device node in /dev/mapper, so cryptsetup should
be fine with that (I haven't tried it though).
The latest version doesn't run vol_id for read-only devices, as before
Is that right, I wonder? At least the cryptsetu
I was about to report this exact same bug, and my patch is the same too.
Without the patch, boot pauses for 3 minutes on a system with encrypted /home.
What normally happens is you enter the disk passphrase, and it would say
it's unlocked and continue booting immediately. But recently, you enter
It makes 'cryptsetup luksOpen' hang for 3 minutes while waiting for
/dev/mapper/temporary-crypsetup- to appear before it times out with
the message "Rendezvous with udev timed out for 'temporary-
cryptsetup-27258'; stat failed: No such file or directory" (it does
succeed after the timeout, though).
Could you explain why you think this is a bug?
This prevents vol_id being run on read-only devices, and thus prevents
any filesystem on them from being automatically used by udev.
Isn't this exactly what this flag is supposed to do?
--
udev rules don't create device nodes for readonly devices
h
** Tags added: patch
--
udev rules don't create device nodes for readonly devices
https://bugs.launchpad.net/bugs/117089
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
