local filesystems: regression from autofs4 to autofs5

local filesystems: regression from autofs4 to autofs5

[Guillaume Rousse]

I've got troubles on a host with autofs v5, where all local file access
to a NFS-exported filesystem triggers a new mount:

/home/graves/clerger on /home/graves/clerger type none (rw,bind)
/home/graves/clerger/ParserRuns on /home/graves/clerger/ParserRuns type
none (rw,bind)
/home/graves/clerger/ParserRuns/results5 on
/home/graves/clerger/ParserRuns/results5 type none (rw,bind)
/home/graves/clerger/ParserRuns/results5/dbdir on
/home/graves/clerger/ParserRuns/results5/dbdir type none (rw,bind)
/home/graves/clerger/ParserRuns/results5/dbdir/mine.dat on
/home/graves/clerger/ParserRuns/results5/dbdir/mine.dat type none (rw,bind)
/home/graves/clerger/fom-meta on /home/graves/clerger/fom-meta type none
(rw,bind)
/home/graves/clerger/fom-meta/config on
/home/graves/clerger/fom-meta/config type none (rw,bind)
...

/etc/fstab says:
/dev/hda7       /home/graves    ext3    defaults 1 2

LDAP says:
# auto.home.graves, autofs, village.inria.fr
dn: ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
objectClass: top
objectClass: automountMap
ou: auto.home.graves

# /, auto.home.graves, autofs, village.inria.fr
dn: cn=/,ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
objectClass: top
objectClass: automount
cn: /
automountInformation: -fstype=nfs,hard,intr,nosuid,nfsvers=3
graves:/home/graves/&

This seems to be a regression compared to autofs v4, where this was not
occuring. The kernel is 2.6.17-6mdv, based on 2.6.17.14.

Re: local filesystems: regression from autofs4 to autofs5

[Ian Kent]

On Mon, 2006-11-27 at 10:53 +0100, Guillaume Rousse wrote:
> I've got troubles on a host with autofs v5, where all local file access
> to a NFS-exported filesystem triggers a new mount:

All local file accesses?
So are you saying accessing /etc or /var will mount everything in the
map below?

What process is requesting the mounts?

> 
> /home/graves/clerger on /home/graves/clerger type none (rw,bind)
> /home/graves/clerger/ParserRuns on /home/graves/clerger/ParserRuns type
> none (rw,bind)
> /home/graves/clerger/ParserRuns/results5 on
> /home/graves/clerger/ParserRuns/results5 type none (rw,bind)
> /home/graves/clerger/ParserRuns/results5/dbdir on
> /home/graves/clerger/ParserRuns/results5/dbdir type none (rw,bind)
> /home/graves/clerger/ParserRuns/results5/dbdir/mine.dat on
> /home/graves/clerger/ParserRuns/results5/dbdir/mine.dat type none (rw,bind)
> /home/graves/clerger/fom-meta on /home/graves/clerger/fom-meta type none
> (rw,bind)
> /home/graves/clerger/fom-meta/config on
> /home/graves/clerger/fom-meta/config type none (rw,bind)
> ...
> 
> /etc/fstab says:
> /dev/hda7       /home/graves    ext3    defaults 1 2
> 
> LDAP says:
> # auto.home.graves, autofs, village.inria.fr
> dn: ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
> objectClass: top
> objectClass: automountMap
> ou: auto.home.graves
> 
> # /, auto.home.graves, autofs, village.inria.fr
> dn: cn=/,ou=auto.home.graves,ou=autofs,dc=village,dc=inria,dc=fr
> objectClass: top
> objectClass: automount
> cn: /
> automountInformation: -fstype=nfs,hard,intr,nosuid,nfsvers=3
> graves:/home/graves/&
> 
> This seems to be a regression compared to autofs v4, where this was not
> occuring. The kernel is 2.6.17-6mdv, based on 2.6.17.14.
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs