Public bug reported:

Binary package hint: cryptsetup

i have set up /etc/crypttab:
# <target name> <source device>         <key file>      <options>
hda10           /dev/hda10              /root/mdp_p2p   luks

and /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults         0       0
/dev/hda1       none            swap    sw               0       0
/dev/hda8       /               reiserfs notail          0       1
/dev/hda2       /media/hda2     ntfs    defaults,nls=utf8,umask=007,gid=46 0    
1
/dev/hda5       /media/hda5     xfs     defaults         0       0
/dev/hda6       /media/hda6     reiserfs defaults        0       2
/dev/hda7       /media/hda7     vfat    defaults,utf8,umask=007,gid=46 0       
1/dev/hda9       /media/hda9     reiserfs defaults        0       2
/dev/mapper/hda10 /media/hda10  xfs     defaults         0       0

and at boot, cryptdisks says [OK] but my crypted partitions is not
available, neither it has been mounted (it should have been isn't it ?)

when i look at cryptdisks, it seems buggy to me. 
line 46:
$DEVMAPCMD mknodes

it creates (for me) hda1,...,hda10 nodes in /dev/mapper. why ? those
nodes must be set up by cryptsetup.

and these nodes make the test line 57
if test -b $MAPPER/$dst; then
succeed and no partitions are mounted ! 

i have commented line 46. but that does not work either. because hda10
nodes is not created. why ?

if i run manually (with modified cryptdisks script) i got :
[~]# /etc/init.d/cryptdisks stop
 * Stopping crypto disks...                                                     
                     [ ok ]
[~]# /etc/init.d/cryptdisks start
 * Starting crypto disks...
 - INSECURE MODE FOR /root/mdp_p2p
key slot 0 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
                                                                         [ ok ]
[~]# ls /dev/mapper/
control
[~]# /etc/init.d/cryptdisks stop
 * Stopping crypto disks...                                                     
                     [ ok ]
[~]# /etc/init.d/cryptdisks start
 * Starting crypto disks...
 - INSECURE MODE FOR /root/mdp_p2p
key slot 0 unlocked.
Command successful.

WHY did the first crypsetup failed with an ioctl error ??? and note the
error but there is still an [OK] displayed. funny isn't it ?

** Affects: cryptsetup (Ubuntu)
     Importance: Untriaged
         Status: Unconfirmed

-- 
cryptdisks script does not work (with luks partitions)
https://launchpad.net/bugs/56120

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to