Forceful unmouting of file systems

[Anuraag]

I mounted a network file system on a TRU64 box. I didn't unmount it. The other machine has gone for a shutdown. Now on the TRU64 box the df command hangs saying the NFS3 server is not responding. Kindly suggest a solution for the same.

[Victor Semaska_3]

Anuraag,

umount -f

man umount for details.

Vic

[Ivan Ferreira]

Also, next time you mount an NFS file system, mount with the options:

-o soft,bg

or

-o hard,intr

[Anuraag]

I tried -f but it didnt unmount. Pls suggest more ideas.

[Ivan Ferreira]

Did you run:

umount -f /filesystem?

If you want to avoid df hang and you cannot umount the file system, you can use:

df -t advfs

[Frank Gessner]

try to clean up from processes hanging on that filesystem first with /usr/sbin/fuser -cuk /your_mountpoint

regards, Frank

[Al Licause]

An interesting tip from a customer stated that when an nfs server becomes unavailable and the client can't proceed with the umount, try temporarily changing the local hosts files entry for that nfs server to one that is available. It should allow the umount to complete.

[anandganjihal]

You can use "df -n":

Use this option if it is possible that one or more file systems are in a state such that they will not be able to provide statistics without a long delay (for example, if you have a remote file system on a server that has crashed). If you specify the
-n option, the df command does not request new statistics from the file systems; for some remote file systems, the statistics displayed may be too obsolete to be useful.

- Anand