On Mon, 28 Nov 2005, Hans Deragon wrote: > Ian Kent wrote: > > On Fri, 25 Nov 2005, Hans Deragon wrote: > > > > > > > Greetings. > > > > > > > > > Well, I successfully reproduced the problem of a path sent to auto.net > > > (see > > > below for full description). Attached, the debug output on syslogd. From > > > what I understand of the syslogd logs, the problem occurs before > > > sun_mount() > > > is called. > > > > > > What I did was: > > > > > > cd /net/asterix # Everything is ok. $key=asterix > > > cd asteris-07 # Bug: $key=asterix/asterix-07 > > > > > > Yes. Undoubtably the problem and that will be in the kernel module. > > > > > > > What was passed to auto.net was asterix/asterix-07 at the second 'cd'. > > > > > > I would like to see the output of auto.net run manually and with the > > incorrect key please. > > > > Do you have access to the source for for the kernel you are using so that we > > may check the patch levels? > > > > Ian > > Greetings Ian. > > > Here is the output of auto.net. > > [EMAIL PROTECTED] etc] auto.net asterix/asterix-07 > /usr/sbin/showmount: can't get address for asterix/asterix-07 > [EMAIL PROTECTED] etc] auto.net asterix > -fstype=nfs,hard,intr,nodev,nosuid \ > /asterix-00 asterix:/asterix-00 \ > /asterix-01 asterix:/asterix-01 \ > /asterix-02 asterix:/asterix-02 \ > /asterix-03 asterix:/asterix-03 \ > /asterix-04 asterix:/asterix-04 \ > /asterix-05 asterix:/asterix-05 \ > /asterix-06 asterix:/asterix-06 > > Please note that in my previous email, when I reproduced > the problem, I used a patched auto.net which would remove > the path. This is not the case above, since I wanted to > reproduce the problem for you. > > This said, I just realized that the recursive path problem > occurs when I try to 'cd' to an NFS share that does not > exist (I have not realized this earlier; my bad). For > instance, with my patched auto.net, > /net/asterix/asterix-07 mounts with the content of > /net/asterix, which is wrong. It should not mount. > > So I am starting to realize that maybe there is no bug... > If I leave auto.net untouched, I do get the proper error, > i.e.: > > [EMAIL PROTECTED] /net/asterix] cd asterix-07 > -bash: cd: asterix-07: No such file or directory > > Yet... I think that auto.net should not receive a path. > So there might be a bug, but a minor one?
Yep. I think that this may be a known problem. I need to review and possibly re-test a patch that I've done recently before I post it. I suspect that it may have broken the expiry. > > I would need to find a case where a path is sent to > auto.net when trying to access a valid NFS share. > > Attached, the auto.net, unpatched (actually, my patch is > commented out). > > Also, I do have the kernel's source. Could you tar the fs/autofs4 directory and send it over so I can check it. There have been several patches lately and I'd like to confirm which have been applied. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
