Using autofs 5.0.6 I am wondering how timeouts works. Should continued use of an automounted filesystem prevent automount from timing out the mount and unmounting it? I ask because I see a strange flapping of one (and only one) of my automounted filesystems. For example, the NFS server serving it reports the following unmount/mount activity for the last few hours. Oct 11 06:55:51 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:746 for /home/share (/home) Oct 11 07:02:05 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:686 for /home/share (/home) Oct 11 07:02:07 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:908 for /home/share (/home) Oct 11 07:08:20 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:808 for /home/share (/home) Oct 11 07:08:23 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:888 for /home/share (/home) Oct 11 07:14:35 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:944 for /home/share (/home) Oct 11 07:14:39 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:861 for /home/share (/home) Oct 11 07:20:50 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:616 for /home/share (/home) Oct 11 07:20:51 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:787 for /home/share (/home) Oct 11 07:27:05 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:702 for /home/share (/home) Oct 11 07:27:07 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:958 for /home/share (/home) Oct 11 07:33:20 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:788 for /home/share (/home) Oct 11 07:33:23 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:827 for /home/share (/home) Oct 11 07:39:35 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:902 for /home/share (/home) Oct 11 07:39:39 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:904 for /home/share (/home) Oct 11 07:45:50 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:977 for /home/share (/home) Oct 11 07:45:51 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:905 for /home/share (/home) Oct 11 07:52:05 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:871 for /home/share (/home) Oct 11 07:52:07 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:868 for /home/share (/home) Oct 11 07:58:20 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:971 for /home/share (/home) Oct 11 07:58:23 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:837 for /home/share (/home) Oct 11 08:04:35 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:616 for /home/share (/home) Oct 11 08:04:39 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:908 for /home/share (/home) Oct 11 08:10:50 linux rpc.mountd[23986]: authenticated unmount request from 10.75.22.1:727 for /home/share (/home) Oct 11 08:10:51 linux rpc.mountd[23986]: authenticated mount request from 10.75.22.1:1000 for /home/share (/home) This is just a small sample but this goes on 24x7. I have a number of other automounted filesystems that seem to stay mounted forever without any of this flapping so somehow automount is able to maintain those mounts stably. My auto.master looks like: /net -hosts /autohome /etc/auto.home /- /etc/auto.global --timeout=300 The auto.home entry for the above mount is: share -rw,intr,rsize=8192,wsize=8192 linux:/home/share The process that seems to be responsible for the continued activity on that mount (i.e. the one that is attributed to causing automount to mount it after it's been umounted is "Thunar" which is a GUI desktop file manager type of tool. But given that the mount request happens within seconds of the unmount I'd expect that while mounted Thunar is causing activity every few seconds which I would hope would cause automount to keep the filesystem mounted. Any ideas? Cheers, b.
Attachment:
signature.asc
Description: OpenPGP digital signature
