Bug 186454
Summary: | autofs never umounts /net/host/dir | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | H.J. Lu <hongjiu.lu> | ||||||||
Component: | autofs | Assignee: | Ian Kent <ikent> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 5 | CC: | dancy, jkf385, jmoyer, k.georgiou, urorzm+bugzilla.redhat.com | ||||||||
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-22 02:36:11 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: | |||||||||||
Attachments: |
|
Description
H.J. Lu
2006-03-23 17:49:12 UTC
It only happens when host exports more subdirectories: gnu-1:/export 59106976 46132392 9972040 83% /net/gnu-1/export gnu-1:/export/server 76920416 19143280 57773040 25% /net/gnu-1/export/server This happens to me as well, under the same circumstances (host exports multiple filesystems). autofs never times out the mounts. killall -v -USR1 automount does cause the unused filesystems to be unmounted. Ian, do you want to take a look at this? (In reply to comment #0) > With autofs-4.1.4-16.2.2, autofs never umounts /net/host/dir after I did > > # cd /net/host/dir > # ls > # cd / I'm really going to need more information on this. Could you have a look at Jeff Moyers people page and put together the version information and a debug log as decsribed their please. Ian is referring to this URL: http://people.redhat.com/jmoyer/ thanks. Created attachment 127931 [details]
/var/log/debug
In /var/log/messages:
Apr 18 08:56:36 gnu-10 automount[9463]: starting automounter version
4.1.4-16.2.2, path = /net, maptype = program, mapname = /etc/auto.net
Apr 18 08:56:36 gnu-10 automount[9463]: using kernel protocol version 4.07
Apr 18 08:56:36 gnu-10 automount[9463]: using timeout 60 seconds; freq 15 secs
Apr 18 08:56:59 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9501]: rm_unwanted: /net/gnu-1/export
Apr 18 08:58:05 gnu-10 automount[9501]: rm_unwanted: /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9501]: expired /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9522]: rm_unwanted: /net/gnu-1/export
Apr 18 08:59:20 gnu-10 automount[9522]: rm_unwanted: /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9522]: expired /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9542]: rm_unwanted: /net/gnu-1/export
Apr 18 09:00:35 gnu-10 automount[9542]: rm_unwanted: /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9542]: expired /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9571]: rm_unwanted: /net/gnu-1/export
Apr 18 09:02:50 gnu-10 automount[9571]: rm_unwanted: /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9571]: expired /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Created attachment 127932 [details]
/var/log/debug
In /var/log/messages:
Apr 18 08:56:36 gnu-10 automount[9463]: starting automounter version
4.1.4-16.2.2, path = /net, maptype = program, mapname = /etc/auto.net
Apr 18 08:56:36 gnu-10 automount[9463]: using kernel protocol version 4.07
Apr 18 08:56:36 gnu-10 automount[9463]: using timeout 60 seconds; freq 15 secs
Apr 18 08:56:59 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9501]: rm_unwanted: /net/gnu-1/export
Apr 18 08:58:05 gnu-10 automount[9501]: rm_unwanted: /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9501]: expired /net/gnu-1
Apr 18 08:58:05 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9522]: rm_unwanted: /net/gnu-1/export
Apr 18 08:59:20 gnu-10 automount[9522]: rm_unwanted: /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9522]: expired /net/gnu-1
Apr 18 08:59:20 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9542]: rm_unwanted: /net/gnu-1/export
Apr 18 09:00:35 gnu-10 automount[9542]: rm_unwanted: /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9542]: expired /net/gnu-1
Apr 18 09:00:35 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9571]: rm_unwanted: /net/gnu-1/export
Apr 18 09:02:50 gnu-10 automount[9571]: rm_unwanted: /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9571]: expired /net/gnu-1
Apr 18 09:02:50 gnu-10 automount[9463]: attempting to mount entry /net/gnu-1
kernel-2.6.16-1.2080_FC5 autofs-4.1.4-16.2.2 Created attachment 128157 [details]
Patch which removes the problem
Attached is a patch that one of my coworkers created which remedies the problem
(and probably supplies enough information to get to the root cause).
See also bug 189535 where the same problem is being discussed. (In reply to comment #9) > Created an attachment (id=128157) [edit] > Patch which removes the problem > > Attached is a patch that one of my coworkers created which remedies the problem > (and probably supplies enough information to get to the root cause). > I must admit it's tempting to apply this patch without further fuss as I have commented these calls out in the version 5 development for other less important reasons to see if there's a regression. So I'd really like to wait till I've had a chance to test this out for for a while. The other concern is that this hasn't changed between the FC4 and FC5 packages. So either a recent kernel patch has caused it or a process other than a GUI is responding to filesystem changes which could have further implications. 2.6.16-1.2096_FC4 and autofs-4.1.4-15.1 on FC4 have no problems. I rebuilt and installed autofs-4.1.4-15.1 on FC5. It doesn't solve the problem. I installed 2.6.16-1.2096_FC4 and autofs-4.1.4-15.1 on FC5. The problem still persists. So the cause is somewhere else. After I ran [root@gnu-65 log]# /etc/init.d/haldaemon stop the problem went away. (In reply to comment #14) > After I ran > > [root@gnu-65 log]# /etc/init.d/haldaemon stop > > the problem went away. Excellent work. I really couldn't see anything autofs that would cause this. I'll check into this. Thanks. Ian (In reply to comment #15) > (In reply to comment #14) > > After I ran > > > > [root@gnu-65 log]# /etc/init.d/haldaemon stop > > > > the problem went away. > > Excellent work. > > I really couldn't see anything autofs that would cause this. > I'll check into this. Can you try the latest version of the HAL package please. I believe this problem is fixed. Ian What is the latest verion of HAL? I am runnig hal-0.5.7-3.fc5.1. (In reply to comment #17) > What is the latest verion of HAL? I am runnig hal-0.5.7-3.fc5.1. Sorry, I'm a bit impacient. I see the fix is currently in the Rawhide version. I'll let you know when it makes it into fc5. Ian (In reply to comment #18) > (In reply to comment #17) > > What is the latest verion of HAL? I am runnig hal-0.5.7-3.fc5.1. > > Sorry, I'm a bit impacient. > I see the fix is currently in the Rawhide version. > I'll let you know when it makes it into fc5. > This version of HAL appears to be have been in FC-5 for a while now, sorry I didn't let you know earlier. Can you check that this problem is now resolved. hal-0.5.7-3.fc5.2 fixes the problem. |