Package: libpam-mount Version: 2.16-4 Pam_mount is failing to mount filesystems when the mount point is a polyinstantiated directory.
The problem is only when the polydir itself is used as a mountpoint; there is no problem using a subdirectory inside the polydir. (e.g. If "/data2" is defined as a polydir in /etc/security/pam_namespace.conf, pam_mount succeeds when using /data2/subdir as a mount point, but fails when using /data2 as the mount point.) When the mount fails, lines like the following are logged by both systemd and login (with debugging enabled in pam_mount.conf.xml): (mount.c:250): Mount info: globalconf, user=elinde <volume fstype="cifs" server="stor1" path="data" mountpoint="/data2" cipher="(null)" fskeypath="(null)" fskeycipher="(null)" fskeyhash="(null)" options="multiuser,cruid=elinde,sec=krb5,cifsacl" /> fstab=0 ssh=0 (mount.c:622): data already seems to be mounted at /data2, skipping This bug doesn't exist in the upstream pam-mount project, but was introduced with the patch 0014-Don-t-compare-source-when-checking-if-it-s-already-m.patch starting in Debian's 2.16-4 release (made to address https://bugs.debian.org/799752 and similar issues with encrypted volumes). This bug is also reported for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/1908638 Evan Linde Research Cyberinfrastructure Analyst Oklahoma State University High Performance Computing Center 405-744-1455 http://hpcc.okstate.edu/
