You have been subscribed to a public bug: Binary package hint: libpam-mount
Since I upgraded to Karmic, I noticed the weird fact that my two auto- mounted LUKS-encrypted partitions randomly seemed to disappear from mtab - I had to manually mount them again to use them. I've been using them for several years with all ubuntus so far, never had a problem until now. These partitions are automatically mounted on login via pam_mount. These are the entries in pam_mount.conf.xml: <volume fstype="crypt" path="/dev/sda3" mountpoint="/media/sda3" options="cipher=aes" /> <volume fstype="crypt" path="/dev/sda5" mountpoint="/media/sda5" options="cipher=aes" /> After digging in the logs, I've found that there is some sort of a cron job trying to unmount my two partitions and running every 60 minutes. If the partitions are busy then they survive; if they are not busy, then they are umounted (very weird !!!!!) >From my auth.log I see this every hour: Nov 15 11:17:01 nahuatl CRON[1230]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(pam_mount.c:516): warning: could not obtain password interactively either Nov 15 11:17:01 nahuatl CRON[1230]: pam_unix(cron:session): session closed for user root Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:67): umount messages: Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount: /media/sda5: device is busy. Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): (In some cases useful info about processes that use Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): the device is found by lsof(8) or fuser(1)) Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount /media/sda5 failed with run_sync status 1 Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): Command failed: Device busy Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount.crypt(crypto-dmc.c:168): Could not unload dm-crypt device "/dev/mapper/_dev_sda5", cryptsetup returned HXproc status 240 Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:698): unmount of /dev/sda5 failed Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:67): umount messages: Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount: /media/sda3: device is busy. Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): (In some cases useful info about processes that use Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): the device is found by lsof(8) or fuser(1)) Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount /media/sda3 failed with run_sync status 1 Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): Command failed: Device busy Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:71): umount.crypt(crypto-dmc.c:168): Could not unload dm-crypt device "/dev/mapper/_dev_sda3", cryptsetup returned HXproc status 240 Nov 15 11:17:01 nahuatl CRON[1230]: pam_mount(mount.c:698): unmount of /dev/sda3 failed In my view this is a major bug. A hint or workaround on how to stop this CRON thing from trying to unmount my drives would be greatly appreciated. I've found only this similar reference: http://groups.google.com/group/linux.debian.user.german/browse_thread/thread/1c632245a397f7c9?utoken =JRGmfjsAAAD-4m7bW_nhUf_RRJzb_a9w_ObWXSwL4IOKiU8782Hmp- EH8COufF2SlzXILlU-DjyKjuOEmBHIEfBNJAzzPaif seems to hint that the problem was introduced recently in debian, in libpam_mount 1.27-4 ** Affects: gnome-keyring (Ubuntu) Importance: Medium Status: Triaged ** Affects: gnome-keyring (Debian) Importance: Unknown Status: New -- pam_mount trying to unmount my auto-mounted encrypted partitions every hour via CRON https://bugs.launchpad.net/bugs/483159 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
