Control: tags -1 + confirmed upstream wontfix
14.05.2013 03:04, Chris Dumont wrote:
> Package: autofs
> Version: 5.0.7-3
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
> Upgraded from squeeze to wheezy.
> * What was the outcome of this action?
> With squeeze (and lenny) I was able to use one automount map via ldap to
> nfsmount fileserver:/home on client:/nfs/fileserver/home on remote boxes and
> locally on the fileserver itself. With wheezy on only the fileserver the
> incorrect directory ("/") is automounted. It appears that in trying to be
> "efficient" and using bind mounts autofs is ignoring the fsid parameter in
> /etc/exports.
> * What outcome did you expect instead?
> Like remote clients the fileserver should be able to use the same map and get
> /home automounted.
>
> Thanks,
> Chris
Thank you for the excellent detailed bugreport.
Yes, the version of automount in wheezy has an optimization, it tries
to substitute nfs mount with local bind mount when it sees that the
nfs server is local. And as you observed, it does not always work
correctly.
> $ grep fsid /etc/exports
> /home
> 192.168.1.0/24(ro,fsid=0,no_root_squash,subtree_check,insecure,crossmnt)
Automount does not ignore fsid of the exported filesystem. It does not
_know_ about fsid, since this information isn't (easily) available on
the client side, and the nfs server in use may be something else than
the standard linux nfs server so parsing /etc/exports might not be the
best idea.
I'd say it is a bug, it is wrong optimization, but upstream is quite a
bit difficult to deal with, and I don't want to divirge from upstream
too much, so we're keeping this wrong upstream behavour.
You have to options to compensate for this.
First, you may just disable this optimization altogether. For this,
see `nobind' option in auto.master(5).
And second, better yet (in my opinion), -- you may override just this
mount point for just this client, using a local file map type, and
explicitly pointing there to the right directory being bind-mounted.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
