[pkg-cryptsetup-devel] Bug#544773: Bug#544773: Update to cryptsetup 2:1.0.7-2 breaks booting

Jonas Meurer jonas at freesources.org
Sun Sep 6 00:39:46 UTC 2009


hey,

On 05/09/2009 Paul Millar wrote:
> vedrfolnir:~# ls -l /dev/mapper
> total 0
> crw-rw---- 1 root root 10, 60 2009-09-04 19:06 control
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 sdb2_crypt -> ../dm-0
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-home -> ../dm-6
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-root -> ../dm-1
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-swap_1 -> ../dm-4
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-tmp -> ../dm-5
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-usr -> ../dm-2
> lrwxrwxrwx 1 root root      7 2009-09-04 19:06 vedrfolnir-var -> ../dm-3
> 
> vedrfolnir:~# cat /etc/mtab
> /dev/dm-1 / ext3 rw,errors=remount-ro 0 0
> tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
> proc /proc proc rw,noexec,nosuid,nodev 0 0
> sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
> udev /dev tmpfs rw,mode=0755 0 0
> tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
> devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
> /dev/sda1 /boot ext2 rw 0 0
> /dev/dm-6 /home ext3 rw 0 0
> /dev/dm-5 /tmp ext3 rw 0 0
> /dev/dm-2 /usr ext3 rw 0 0
> /dev/dm-3 /var ext3 rw 0 0
> rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
> fusectl /sys/fs/fuse/connections fusectl rw 0 0
> nfsd /proc/fs/nfsd nfsd rw 0 0
> 
> > i guess that you discovered the same bug as #544487.
> 
> Yes, that bug looks pretty similar.  Certainly the sym. links from /dev/mapper 
> to /dev/dm* mentioned in that bug are also present here.

so indeed the problem here is that files in /dev/mapper are symlinks
rather than devices. i don't know what exactly triggered that change,
but it must be a recent upgrade of some package related to
device-mapper, udev and/or kernel.

nevertheless, we'll need to add support for /dev/dm-* devices in
cryptroot initramfs script/hook. a quick check revealed that dmsetup
doesn't support /dev/dm-* devices as arguments. thus cryptroot needs to
find out the name in /dev/mapper/, regardless whether it's a symlink or
the actual device file.

so i guess that canonical_devie() needs to check whether the device is
something like /dev/dm-* and transform that into the corresponding
/dev/mapper/* device/symlink before returning.

i'll be on holidays until september 18. so i'll not be able to look into
that before.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090906/c4747235/attachment.pgp>


More information about the pkg-cryptsetup-devel mailing list