(This takes into account the mail you sent by private email.) >Feb 19 20:21:52 MYHOSTNAME login[4568]: pam_mount(mount.c:64): umount >messages: >Feb 19 20:21:52 MYHOSTNAME login[4568]: pam_mount(mount.c:67): Command >failed: Device busy
Well that comes from umount(8). If your disk is still used, there is no way we can unmount it. So it's not really a pam_mount issue... >The function ehd_dmcrypt_ops.unload() fails because on top of my LUKS >partition (/dev/mapper/_dev_loop0) a loop device is set up >(/dev/loop1): Then you have to make sure this loop device - which has an inode on the crypto image - is closed. >But why is a loop device attached to my LUKS partition? Because you specified so. Feb 19 20:21:47 MYHOSTNAME login[4568]: pam_mount(mount.c:172): Mount info: globalconf, user=MYUSERNAME <volume fstype="auto" server="(null)" path="/my/encrypted.img" mountpoint="/mnt" cipher="(null)" fskeypath="/my/encrypted.key" fskeycipher="aes-256-cbc" fskeyhash="sha512" options="fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,fsck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essiv:sha256,keybits=256,hash=sha512" /> fstab=0 This yields a mount command of Feb 19 20:21:47 MYHOSTNAME login[4568]: command: [mount] [-p0] [-o] [fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,fsck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essiv:sha256,keybits=256,hash=sha512] [-t] [auto] [/my/encrypted.img] [/mnt] And that one does not even work for me on openSUSE/util-linux 2.14.1: 16:15 yaguchi:../pmt/src # mount -p0 -o fsk_cipher=aes-256-cbc,fsk_hash=sha1,keyfile=/home/jengelh/Coding/pmt/src/x.key,fsck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essiv:sha256,keybits=256,hash=sha512 -t auto /home/jengelh/Coding/pmt/src/x.cont /mnt mount: you must specify the filesystem type So it may happen that your Debian mount(8) is either old or does nasty things wrt. loop. Certainly, what it does seems coherent though: >/dev/loop0: [0901]:14450726 (/my/encrypted.img) >/dev/loop1: [000d]:30967 (/dev/mapper/_dev_loop0) (a) mount creates a loop device /dev/loop0 from encrypted.img (b) mount.crypt gets /dev/loop0 as first parameter... (c) umount does not call crypt or so.. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
