On Tue, 02 Dec 2008 11:19:04 +0100, Pavel Filipensky <Pavel.Filipensky at sun.com> wrote:
> Interesting. The root cause is in /usr/sbin/umountall and how it > processes /etc/mnttab. > E.g. we have mounted NFS file system on mountpoint > /net/tb3.uk/tank/src/onnv-snapshots/onnv_66 > via autofs: > > /etc/mnttab will contain these 2 lines: > > tb3.uk:/tank/src/onnv-snapshots/onnv_66 > /net/tb3.uk/tank/src/onnv-snapshots/onnv_66 nfs > -hosts /net/tb3.uk/tank/src/onnv-snapshots/onnv_66 autofs > > /sbin/umountall -l will do this check: > > if [ -n "$LFLAG" -a "$fstype" = "nfs" ]; then > continue > fi > > obviously it will skip nfs, but will proceed with autofs - since both > use the same mountpoint, quite. > the call 'umount -a /net/tb3.uk/tank/src/onnv-snapshots/onnv_66' does > not know that it should > do the 'autofs' unmount (which should return EBUSY) and will do the 'nfs > 'unmount and will hang. though eventually I'd like to see forcible unmounts supported in autofs, ie. autofs should attempt to forcibly unmount its triggered mounts, ie. in the scope of NFS, do an NFS forcible umount. we could use that to deal with the general aspects of a dead server/down network in a later course of action. > The fix "6675447 NFSv4 client hangs on shutdown if server is down > beforehand" > is not working for autofs/nfs mounts - must be reopened. I'd rather like to see a new bug opened, will do so in a minute. --- frankB
