Bug 193832
| Summary: | New autofs failes to remount /net maps after expiry | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen Tweedie <sct> |
| Component: | autofs | Assignee: | Ian Kent <ikent> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | jmoyer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-06-16 00:27:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
(In reply to comment #0) > Description of problem: > After upgrading a working rawhide to autofs-5.0.0-beta, /net now fails to > remount subdirectories if the mount times out and expires, as near as I can make > out. I thought I'd fixed this with revision 6. Obviously not. I'll get right on it. Ian (In reply to comment #1) > (In reply to comment #0) > > Description of problem: > > After upgrading a working rawhide to autofs-5.0.0-beta, /net now fails to > > remount subdirectories if the mount times out and expires, as near as I can make > > out. > > I thought I'd fixed this with revision 6. > Obviously not. I'm not certain but I believe I've fixed this while sorting out the issue with the wildcard entry in maps. I found a place where I failed to release a mutex during expire runs. I must have made this blunder fairly recently as I would have noticed it earlier. So please check autofs-5.0.0_beta4-1 (when it appears on the mirrors) and see if it resolves this problem. Ian A local build of autofs-5.0.0_beta4-1 shows exactly the same problem. It appears that the lookup_mount is failing to construct the correct hostname to pass to /usr/sbin/showmount: the errors Jun 1 23:15:23 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: can't get address for sisko/kickstart Jun 1 23:15:23 ghost automount[7290]: lookup_mount: lookup(program): lookup for sisko/kickstart failed indicate that the hostname being passed to showmount is mistakenly getting the first component of the pathname appended to it. And indeed, running showmount with the same arguments at the command line shows the same errors. (In reply to comment #3) > A local build of autofs-5.0.0_beta4-1 shows exactly the same problem. > > It appears that the lookup_mount is failing to construct the correct hostname to > pass to /usr/sbin/showmount: the errors > > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: > can't get address for sisko/kickstart > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: lookup(program): lookup for > sisko/kickstart failed > > indicate that the hostname being passed to showmount is mistakenly getting the > first component of the pathname appended to it. And indeed, running showmount > with the same arguments at the command line shows the same errors. > OK. I'll try harder to duplicate this. Can you outline what you're doing to give me something to work with please? Ian (In reply to comment #4) > (In reply to comment #3) > > OK. I'll try harder to duplicate this. > Can you outline what you're doing to give me something to > work with please? Ignore this you've got the detail above. Ian (In reply to comment #4) > (In reply to comment #3) > > A local build of autofs-5.0.0_beta4-1 shows exactly the same problem. > > > > It appears that the lookup_mount is failing to construct the correct hostname to > > pass to /usr/sbin/showmount: the errors > > > > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: > > can't get address for sisko/kickstart > > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: lookup(program): lookup for > > sisko/kickstart failed Also could you provide the output from "showmount -e sisko" please. I'll setup similar here and see if I can duplicate it. Ian (In reply to comment #6) > (In reply to comment #4) > > (In reply to comment #3) > > > A local build of autofs-5.0.0_beta4-1 shows exactly the same problem. > > > > > > It appears that the lookup_mount is failing to construct the correct hostname to > > > pass to /usr/sbin/showmount: the errors > > > > > > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: > > > can't get address for sisko/kickstart > > > Jun 1 23:15:23 ghost automount[7290]: lookup_mount: lookup(program): lookup for > > > sisko/kickstart failed > > Also could you provide the output from "showmount -e sisko" please. > I'll setup similar here and see if I can duplicate it. > Got it. In fact it dawned on me while I was thinking about it. I'm not cleaning up after myself properly, leaving stale mount point directories around and letting the umount of the autofs filesystem do it. This was an experiment that appeared to work but obviously it's a bad idea. Mostly it's not a problem except in some specific cases, like this one. I'll need to check this out a bit further but I should have something by Monday. Thanks for your patience. Ian (In reply to comment #8) > > Also could you provide the output from "showmount -e sisko" please. > > I'll setup similar here and see if I can duplicate it. > > > > Got it. > > In fact it dawned on me while I was thinking about it. > I'm not cleaning up after myself properly, leaving stale mount > point directories around and letting the umount of the autofs > filesystem do it. This was an experiment that appeared to work > but obviously it's a bad idea. Mostly it's not a problem except > in some specific cases, like this one. > > I'll need to check this out a bit further but I should have > something by Monday. Hi Stephen, Could you try autofs-5.0.0_beta4-3 either from CVS or when it hits the mirrors please. It's in the build queue now. Ian Hi Stephen, fyi, still shaking out problems with multi-mounts, see bz# 194069. Ian In my own config, which mixes top-level and deeper exports, autofs-5.0.0_beta4-3 (built locally from CVS) fixes this entirely --- thanks! (In reply to comment #11) > In my own config, which mixes top-level and deeper exports, autofs-5.0.0_beta4-3 > (built locally from CVS) fixes this entirely --- thanks! > Thanks Stephen, I'll leave this open a little longer as I'm working on some related corrections which may impact you. If I don't hear anything within a few after the update reaches the mirrors I'll assume all is OK. Ian |
Description of problem: After upgrading a working rawhide to autofs-5.0.0-beta, /net now fails to remount subdirectories if the mount times out and expires, as near as I can make out. I'm using a standard /etc/auto.net, and accessing it via /net/$host/disk/new where $host is a short hostname listed in the NIS hosts map. Immediately after restarting autofs, I can see this mount. But if I wait a while, it becomes inaccessible, becoming available again only after restarting autofs. Version-Release number of selected component (if applicable): glibc-2.4.90-10 autofs-5.0.0_beta3-6 kernel-2.6.16-1.2232_FC6xen0 How reproducible: 100% Steps to Reproduce: 1. ls /net/$somehost/$some/$dir 2. wait 3. ls /net/$somehost/$some/$dir Actual results: # ls /net/$somehost/$some/$dir ls: /net/$somehost/$some/$dir: No such file or directory on second "ls" Expected results: "ls" should work both times. Additional info: After service autofs restart I can once again access the mount, for a while. When the re-access fails, it is always accompanied by a log message complaining, for example: Jun 1 23:04:50 ghost automount[5410]: lookup_mount: >> /usr/sbin/showmount: can't get address for $somehost/$some ie. it is trying to lookup the host AND the prefix of the subdirectory pathname as a hostname, and failing. This fails for top-level maps on a host as well as for subdirectories: [root@ghost ~]# ls /net/sisko/kickstart [WORKS] [root@ghost ~]# ls /net/sisko/disk/new/ [WORKS] ... wait ... [root@ghost ~]# ls /net/sisko/kickstart ls: /net/sisko/kickstart: No such file or directory [root@ghost ~]# ls /net/sisko/disk/new/ ls: /net/sisko/disk/new/: No such file or directory leaving behind Jun 1 23:15:23 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: can't get address for sisko/kickstart Jun 1 23:15:23 ghost automount[7290]: lookup_mount: lookup(program): lookup for sisko/kickstart failed Jun 1 23:15:40 ghost automount[7290]: lookup_mount: >> /usr/sbin/showmount: can't get address for sisko/disk Jun 1 23:15:40 ghost automount[7290]: lookup_mount: lookup(program): lookup for sisko/disk failed in the logs.