Comment 0 for bug 588523

Binary package hint: autofs

We use cascading mounts to reduce the number of NFS mounts. Consider the following situation: When a user accesses /home/<username>, all homes exported on our file server should be mounted at /net/user (via NFS) if it didn't happen earlier. After that, the directory /net/user/<username> should be bind to /home/<username> (via a local bind mount). This cascading automount configuration could look as follows (In reality, we use autofs5-ldap and LDAP maps, but I checked with the following configuration as well):

Contents of auto.master:
/- auto.direct
/home auto.home

Contents of auto.direct:
/net/user -rw fileserver:/home/user

Contents of auto.home:
* -rw :/net/user/&

Expected behavior: As described above.

Observed behavior: Bind mounts failed with the package autofs5_5.0.4-3.1ubuntu5_i386 in lucid because the NFS mount was not executed beforehand (the debug logs tell about a non-existing special device).
However, everything works as expected if using the compile option
DISABLE_MOUNT_LOCKING
and building an adapted deb package.

$ automount -V
Linux automount version 5.0.4

Directories:
 config dir: /etc/default
 maps dir: /etc
 modules dir: /usr/lib/autofs

Compile options:
  DISABLE_MOUNT_LOCKING ENABLE_FORCED_SHUTDOWN ENABLE_IGNORE_BUSY_MOUNTS
  WITH_HESIOD WITH_LDAP WITH_SASL LIBXML2_WORKAROUND

$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04