After installing autofs-5.0.6 and restarting autofs, the information of mounted shares seems to be broken after first access: With the first NFS server: ========================== root@lynx:/root(10)# /etc/init.d/autofs restart; for ((i=0; i<3 ; i++)) { echo "--------------- i-$i -----------"; ll /net/moose/ ; sleep 1; } * Stopping automounter ... [ ok ] * Starting automounter ... [ ok ] --------------- i-0 ----------- /bin/ls: /net/moose/var: No such file or directory /bin/ls: /net/moose/home_moose: No such file or directory /bin/ls: /net/moose/data_moose: No such file or directory total 0 drwxr-xr-x 2 root root 0 Jun 30 13:24 data_moose/ drwxr-xr-x 2 root root 0 Jun 30 13:24 home_moose/ drwxr-xr-x 2 root root 0 Jun 30 13:24 usr/ drwxr-xr-x 2 root root 0 Jun 30 13:24 var/ --------------- i-1 ----------- /bin/ls: cannot access /net/moose/var: No such file or directory /bin/ls: cannot access /net/moose/home_moose: No such file or directory /bin/ls: cannot access /net/moose/data_moose: No such file or directory total 0 d????????? ? ? ? ? ? data_moose/ d????????? ? ? ? ? ? home_moose/ drwxr-xr-x 4 root root 0 Jun 30 13:24 usr/ d????????? ? ? ? ? ? var/ --------------- i-2 ----------- /bin/ls: cannot access /net/moose/var: No such file or directory /bin/ls: cannot access /net/moose/home_moose: No such file or directory /bin/ls: cannot access /net/moose/data_moose: No such file or directory total 0 d????????? ? ? ? ? ? data_moose/ d????????? ? ? ? ? ? home_moose/ drwxr-xr-x 4 root root 0 Jun 30 13:24 usr/ d????????? ? ? ? ? ? var/ With the second NFS server: ========================== root@lynx:/root(11)# /etc/init.d/autofs restart; for ((i=0; i<3 ; i++)) { echo "--------------- i-$i -----------"; ll /net/cheetah/ ; sleep 1; } * Stopping automounter ... [ ok ] * Starting automounter ... [ ok ] --------------- i-0 ----------- /bin/ls: /net/cheetah/var: No such file or directory /bin/ls: /net/cheetah/home_cheetah: No such file or directory /bin/ls: /net/cheetah/data_cheetah: No such file or directory total 0 drwxr-xr-x 2 root root 0 Jun 30 13:24 data_cheetah/ drwxr-xr-x 2 root root 0 Jun 30 13:24 home_cheetah/ drwxr-xr-x 2 root root 0 Jun 30 13:24 usr/ drwxr-xr-x 2 root root 0 Jun 30 13:24 var/ --------------- i-1 ----------- /bin/ls: cannot access /net/cheetah/var: No such file or directory /bin/ls: cannot access /net/cheetah/home_cheetah: No such file or directory /bin/ls: cannot access /net/cheetah/data_cheetah: No such file or directory total 0 d????????? ? ? ? ? ? data_cheetah/ d????????? ? ? ? ? ? home_cheetah/ drwxr-xr-x 4 root root 0 Jun 30 13:24 usr/ d????????? ? ? ? ? ? var/ --------------- i-2 ----------- /bin/ls: cannot access /net/cheetah/var: No such file or directory /bin/ls: cannot access /net/cheetah/home_cheetah: No such file or directory /bin/ls: cannot access /net/cheetah/data_cheetah: No such file or directory total 0 d????????? ? ? ? ? ? data_cheetah/ d????????? ? ? ? ? ? home_cheetah/ drwxr-xr-x 4 root root 0 Jun 30 13:24 usr/ d????????? ? ? ? ? ? var/
I see this issue at several systems, e.g.: root@inspironM12:/root(38)# /etc/init.d/autofs restart; for ((i=0; i<3 ; i++)) { echo "--------------- i-$i -----------"; ll /net/moose/ ; sleep 1; } * Stopping automounter ... [ ok ] * Starting automounter ... [ ok ] --------------- i-0 ----------- /bin/ls: /net/moose/var: No such file or directory /bin/ls: /net/moose/home_moose: No such file or directory /bin/ls: /net/moose/data_moose: No such file or directory total 0 drwxr-xr-x 2 root root 0 Jun 30 14:08 data_moose/ drwxr-xr-x 2 root root 0 Jun 30 14:08 home_moose/ drwxr-xr-x 2 root root 0 Jun 30 14:08 usr/ drwxr-xr-x 2 root root 0 Jun 30 14:08 var/ --------------- i-1 ----------- /bin/ls: cannot access /net/moose/var: No such file or directory /bin/ls: cannot access /net/moose/home_moose: No such file or directory /bin/ls: cannot access /net/moose/data_moose: No such file or directory total 0 d????????? ? ? ? ? ? data_moose/ d????????? ? ? ? ? ? home_moose/ drwxr-xr-x 4 root root 0 Jun 30 14:08 usr/ d????????? ? ? ? ? ? var/ --------------- i-2 ----------- /bin/ls: cannot access /net/moose/var: No such file or directory /bin/ls: cannot access /net/moose/home_moose: No such file or directory /bin/ls: cannot access /net/moose/data_moose: No such file or directory total 0 d????????? ? ? ? ? ? data_moose/ d????????? ? ? ? ? ? home_moose/ drwxr-xr-x 4 root root 0 Jun 30 14:08 usr/ d????????? ? ? ? ? ? var/ I have the following auto.master: root@inspironM12:/root(39)# cat /etc/autofs/auto.master # $Id: autofs5-auto.master,v 1.1 2011/05/23 08:29:05 pva Exp $ # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). # /misc /etc/autofs/auto.misc #/net /etc/autofs/auto.net # #/home /etc/autofs/auto.home /disk /etc/autofs/auto.home # NOTE: mounts done from a hosts map will be mounted with the # "nosuid" and "nodev" options unless the "suid" and "dev" # options are explicitly given. # /net -hosts # # Include central master map if it can be found using # nsswitch sources. # # Note that if there are entries for /net or /misc (as # above) in the included master map any keys that are the # same will not be seen as the first read key seen takes # precedence. # +auto.master
After downgrading to autofs-5.0.5-r5 autofs works again as expected: >>> Installing (1 of 1) net-fs/autofs-5.0.5-r5 * checking 62 files for package collisions >>> Merging net-fs/autofs-5.0.5-r5 to / ... root@lynx:/root(21)# /etc/init.d/autofs restart; for ((i=0; i<3 ; i++)) { echo "--------------- i-$i -----------"; ll /net/cheetah/ ; sleep 1; } * Caching service dependencies ... ############################################################## 99servers.sh: CUR_RUNLEVEL=|3| PREV_RUNLEVEL=|N| ############################################################## [ ok ] * Stopping automounter ... [ ok ] * Starting automounter ... [ ok ] --------------- i-0 ----------- total 0 drwxr-xr-x 2 root root 0 Jun 30 14:55 data_cheetah/ drwxr-xr-x 2 root root 0 Jun 30 14:55 home_cheetah/ drwxr-xr-x 2 root root 0 Jun 30 14:55 usr/ drwxr-xr-x 2 root root 0 Jun 30 14:55 var/ --------------- i-1 ----------- total 13 drwxr-xr-x 7 root root 4096 Jan 7 19:29 data_cheetah/ drwxr-xr-x 12 root root 4096 Jan 7 12:57 home_cheetah/ drwxr-xr-x 30 root root 4096 Apr 18 04:46 usr/ drwxr-xr-x 21 root root 512 May 11 2010 var/ --------------- i-2 ----------- total 13 drwxr-xr-x 7 root root 4096 Jan 7 19:29 data_cheetah/ drwxr-xr-x 12 root root 4096 Jan 7 12:57 home_cheetah/ drwxr-xr-x 30 root root 4096 Apr 18 04:46 usr/ drwxr-xr-x 21 root root 512 May 11 2010 var/
Created attachment 278703 [details, diff] autofs-5.0.6-ipv6_name_lookup_regression.patch This is probably due to a regression in the ipv6 lookup patch which has been already addressed by upstream. @Peter: Please remove autofs-5.0.6.ebuild and rev bump to autofs-5.0.6-r1 to include upstream patch which I will attach to this bug. I will attach a diff to include the patch to the ebuild as well. @Juergen: Please test after the new ebuild is in the tree whether it solves this issue
Created attachment 278705 [details, diff] autofs-5.0.6-r1.ebuild.diff
Sorry for the bugspam, still learning to remember how to use new bugzilla... @Peter: please see comment 3. Thanks!
I am still waiting for the autofs-5.0.6-r1.ebuild in the tree.
Thank you guys. autofs-5.0.6-r1.ebuild with the patch is in the tree.
With autofs-5.0.6-r1 the issue disappears.
(In reply to comment #8) > With autofs-5.0.6-r1 the issue disappears. Thanks for the feedback!
