What is the rationale behind closing all /dev/mapper/luks-* devices
which are not 'busy' in this shell script? Why would they have to be
'busy' (I presume already mapped) to be left open?
I am asking this because when the smartcard module opens a LUKS drive
(not root - '/') - this drive later to be mapped from the actual root
/etc/fstab file as '/dev/mapper/luks-XXX /some/directory' - this
operation does not succeed and I presume crypt-cleanup.sh closes it up
before the actual root can get it and therefore it cannot be mapped.
Further to the above, I was able to verify that the above script is
indeed to blame for closing LUKS partitions. The only 'busy' partition
at the time crypt-cleanup.sh runs is the root (/sysroot) so I don't see
how a LUKS partition (other than root) specified at the kernel command
line could be opened, unless I am missing something obvious...
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
