After upgrading from the autofs 3.1.7 to autofs 4.1.3 automounted NFS directories from a server with a RTT ~210ms fail while a server on the LAN continues to work as expected. Mounting the failing exports manually works as expected. After a bit of digging around I discovered that removing the replicated_server_select.patch from the ebuild resolves the issue although at this point I've not had the time to work out exactly what the problem is. # emerge info Portage 2.0.51.22-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.11ac1 i686) ================================================================= System uname: 2.6.11ac1 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.12 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.10 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-mtune=pentium3 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mtune=pentium3 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/gentoo/overlay" SYNC="rsync://gentoo.blueyonder.co.uk" USE="x86 X adns afs alsa apache2 apm avi bash-completion berkdb bitmap-fonts cdr crypt cscope cups curl dba dvdr eds emboss encode esd flac foomaticdb fortran gcj gd gdbm gif gnome gpm gstreamer gtk gtk2 imap imlib java jpeg junit kde kerberos krb4 krb5 ldap libg++ libwww mad mikmod mozilla mp3 mpeg mysql ncurses nls no-suexec nptl ogg oggvorbis opengl oss pam pcre pdflib perl php png python qt quicktime readline samba sasl sdl snmp spell ssl svga tcltk tcpd tiff transarc-paths truetype truetype-fonts type1-fonts unicode vorbis xml2 xmms xprint xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Same here with net-fs/autofs-4.1.3-r7. I couldn't mount any NFS share until I removed the patch and recompiled just mount_nfs.so. When I ran automount with -d (by adding -d to daemonoptions in /etc/conf.d/autofs) I got the following piece of output in syslog when trying to enter an NFS share: Aug 1 10:11:10 paszczak automount[18704]: mount(nfs): nfs options="ro,soft,intr", nosymlink=0 Aug 1 10:11:10 paszczak automount[18704]: mount(nfs): winner = (null) local = 0 Aug 1 10:11:10 paszczak automount[18704]: mount(nfs): no host elected Aug 1 10:11:10 paszczak automount[18704]: failed to mount /mnt/auto/fardir Shouldn't this be sorted out by now? Or at least please add a use flag to skip the patch if it's important, because it seems to be breaking things.
New maintainer, net-fs/autofs-5.0.3-r1 is now in the tree.
The newly introduced ebuild is patchless, so maybe the error that was introduced by the mentioned patch doesn't occur in the autofs-5 ebuild? Please test, any feedback is appreciated
No feedback in well over a month, closing bug.
Apologies for not responding I had forgotten about this, autofs-5.0.3-r1 has resolved the issue for me.
Glad to hear that. Thank you for the response. Stefaan
Re-opening to mark as fixed.
There we go. Sorry for the bugzilla spam.
