Server A used to be a NFS server. Server B was mounting an export of that. Everything was fine. Then A died. Just switched off. Gone. Vanished.
However that folder is still mounted on B. I obviously can't cd
into it or anything. However umount /mnt/myfolder
just hangs and won't umount. Is there anyway to umount it without restarting B?
Both client and server are Linux machines.
Assuming Linux:
Will sort of fix the problem:
-f
Force unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.)-l
Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.)-f
also exists on Solaris and AIX.Elaborating upon the hint given by David Pashley,
unless "umount -l" solves your problem, you can set up a fake server with the same address as the one that has gone away - but you don't actually have to set up a new sever or anything. The easiest way out of the blocking/hung umount situation is to set up a local alias IP interface, as follows:
(obviously 11.22.33.44 being the (former) IP address of the (now dead) NFS server)
It might be wise to add the
intr
option to any/etc/fstab
entries that might end up hanging or crashing. If you don't use thesoft
orintr
options, then when the server hosting the NFS files goes down, the server on which the files are mounted (the client) may hang when booting up.According to
man 5 nfs
:... and then it goes on to say
intr
is preferred oversoft
, but it has the similar effect of preventing hanging.umount -f /mnt/myfolder
should solve this. See the umount manpage.I've never managed to get
umount -f
to work. A useful trick is to set up another server mounting the same export, give it the same IP address as the old server. Your NFS client should think everything is back as normal and processes will unblock. You can then unmount the mount point normally and remove the IP address from the temporary NFS server.Just as an aside, using automount will handle unmounting NFS shares when they become unavaliable, which avoids getting stuck in this situatuion in future.
For Solaris, restarting the NFS client will resolve the "hard mount spiral of death". The command for Solaris 10 is "svcadm restart network/nfs/client" Haven't tried this on a Linux box lately (because those all mount with the "intr" flag so they rarely have this problem), but it probably will also fix the problem.
I just noticed that forcing unmounts on kernel 3.2.0 hangs with NFSv4 mounts. NFSv3 unmounts work fine.
just an OS X-specific follow-up, since mount commands are mostly *nix agnostic: the -l (lazy) flag doesn't exist in OS X, however, the -f (force) flag does, and proved to be sufficient. Also, the system-generated mount points are in /Volumes (/Volumes/myserversexport)
I've met this same problem. Since the NFS server got removed, I can not umount the nfs from client. I tried the following trick, see if it could be helpful. Since the original NFS server is gone, I create a new server with same IP and exports. Then I try umount -f /mnt/nfs_part. I finally could umount the nfs now.