I am having a problem with automounter failures on my Solaris Samba server.
There is an automount path on the server that looks something like this: /dir1/dir2/dir3/dir4 Each dirN is an automount point with its own map. Dir4 contains some data, and some links to other automount points in /net Frequently (more than once per day, on a bad day), the automounter gets confused, or something, and will no longer mount *some* mount points in /net. More factoids follow: - This only happens on the Samba server. - The failed mount points are not always the same, but are always symlinked from .../dir4. - During these failures, the automounter is still working for other directories in /net, .../dir4, and elsewhere - The mount points in /net that are hung are still visible, but are not mounted, which is even more odd since -nobrowse is set for /net - they should not be visible at all if they are not mounted. - Stopping and restarted the automounter, using /etc/init.d/autofs *usually* resolves the problem temporarily. After about 5 or 6 times, however, this no longer works, and the entire system needs to be rebooted. - The system is an Ultra II, running Solaris 2.6 and Samba 2.2.8a Has anybody else experienced anything like this? Any ideas why it happens, or how to solve it? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
