On Tue, 22 Nov 2005, Farkas Levente wrote: > Ian Kent wrote: > > On Mon, 21 Nov 2005, Farkas Levente wrote: > > > > > >>hi, > >>i'm just start autofs on my desktop machine. the main reason for this > >>because smbfs (and also cifs) use a very high network load on my system > >>and i use these file very seldom, so it'd be very useful if after a few > >>minutes these fs can be umounted. unfortunately it seems that neither > >>cifs or smbfs not nfs volumes are never umounted. if they mounted once > >>they will remain there forever. it seems automount has the right option: > >>-------------------------------- > >>root 2007 0.0 0.0 1792 696 ? Ss Nov16 0:00 > >>/usr/sbin/automount --timeout=60 /smb program /etc/auto.smb > >>root 2041 0.0 0.0 1788 696 ? Ss Nov16 0:00 > >>/usr/sbin/automount --timeout=60 /net program /etc/auto.net > >>-------------------------------- > >>i try to find out which file can hold /net or /smb but neither fuser nor > >>lsof can show anything. is there any way to find out something about the > >>status of automount? eg which files are used what is the timeout when > >>the timeout fill be left etc? > >>what can be wrong? any tip? > >>my system is fedora core 4 full update: > >>kernel-2.6.14-1.1637_FC4 > >>autofs-4.1.4-5 > >>nfs-utils-1.0.7-12.FC4 > >>samba-client-3.0.14a-2 > >>thank you for your help in advance. > >>yours. > > > > > > I see this sort of thing from time to time but I have always been > > unable to find out what is causing it. > > > > Are you using a GUI. They are well known for scanning filesystems and > > keeping automounts active. > > > > Maybe I need to alter the autofs definition of busy. I'll think about it. > > the best solution would be some kind of status report. who use it, why > busy, which file(s), when will umount, etc. in this case one can solve > the problem to drop/kill/not use such programs which has such effect. > but without such knowladge i'm just in the dark...
That wasn't what I had in mind. I was thinking more along the lines of the definition of what constitues "use". For example any access, such as a directory listing, will update the "last used" value whereas if I change the definition of "last used" to "currently in use" then to be busy there would have to be an open file or a process working directory set. This may solve the GUI scanning problem we see but wouldn't solve immediate remounting that occurs due to the scanning as well. Most of the info you refer to above is either not available or hard to get. Basically a lot of work. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
