On Fri, 5 May 2006, Neil Millar wrote: > On 05/05/06, Ian Kent <[EMAIL PROTECTED]> wrote: > > On Fri, 5 May 2006, Neil Millar wrote: > > > > > Looking at the debug output i'm less convinced now that it is problems > > > with automount rather than nfs in general, but the return codes may help > > > confirm that? > > > > Yes. That superblock error is a bit suspicious. > > > > However, before we go further please check to see if your autofs package > > includes the patch: > > > > http://www.kernel.org/pub/linux/daemons/autofs/v4/autofs-4.1.4-locking-fix-1.patch > > The suse package doesn't appear to have that patch included. Should > I try that?
I don't think it will solve the problem but I think some of the messages are because the locking is also failing. OTOH the locking could be timing out because NFS umount is blocked. I'd add it and see if we can get rid of some of the error messages and maybe get closer to what's actually happening. Unfortunately, the lock is meant to prevent corruption of /etc/mtab and because it's shared by all mounts and umounts it can't be specific to individual mounts so it affects all mounts. I'd add it anyway. Another way to eliminate unrelated error messages might be to disable the mount locking using: http://www.kernel.org/pub/linux/daemons/autofs/v4/autofs-4.1.4-configureable-locking.patch but you will need to be carefull to ensure that util-linux mount/umount locking is working. SuSE might already have a patched util-linux. See the patch for more information. The reason this is better is because it moves the locking of mtab to a much smaller window so the hung mount will not have taken the lock since it probably hasn't umounted the file system yet. So other unrelated mount/umounts won't also then fail. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
