https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c5 --- Comment #5 from Neil Brown <nfbrown@novell.com> 2008-11-20 19:52:06 MST --- If the network has gone away it is still quite possible to do a lazy unmount: umount -alt nfs,nfs4 If any processes are actively using the mountpoints they will block if they every try to access anything, but new processes that try to touch things will get a simple "file not found" until the link comes back up and the nfs filesystems are remounted. If the IP address has changed, it is important to remove the old mount and create a new mount as the old mount will very likely hang even though the network is back. Would it be possible to change dispatcher.d/nfs to do that? It isn't suitable to do "/etc/init.d/nfs stop" as that currently isn't safe if the network is gone. Just an explicit "umount -alt nfs,nfs4" would be best. Sebastian: is it possible to get answers to Comment #4 ?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.