mounted NFS blocks "forever"



Following next steps my mountd NFS partition blocks "forever":

1.- I start the server NFS process.
2.- I mount the NFS partition like:
mount -t nfs 192.168.2.1:/export/home /home
3.- I stop and start the NFS server, simulating a server/network
temporal shutdown.
4.- The mounted partition doesn't work anymore and simple comands
like:

# ls /home

blocks until I "kill-9" them and there is no way to unmount the device
since trying to unmount it returns "device bussy".

Using ps I see for example that ls is stuck in the kernel call to
nfs_wait_schedule:
[root@/]# ps x -o cmd,wchan | grep ls

ls --color=tty /home nfs_wait_schedule

It's there anyway to avoid such behaviour. I would like, in the worst
case when the NFS servers goes down, to be able to unmount and
remount again.

Thanks in advance for any help,hint or link!


P.S.: I'm using kernel 2.6.20-1.2944.fc6
.



Relevant Pages

  • V210 BGE0@1000FDX (Adam Tomkinson)
    ... sunmanagers Digest, Vol 31, Issue 28 ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ...
    (SunManagers)
  • V210 BGE0@1000FDX
    ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ... where hostname is the name of the NFS client which will automount the ...
    (SunManagers)
  • Solved: Perl/NFS "Text File Busy" Error And Related Problems
    ... Â That means I am actually editing the Perl file on ... and I am running it on another (my server). ... The first problem I had was that when I saved my script through NFS, ... apt-get install nfs-kernel-server ...
    (Debian-User)
  • 7.0 RC1 dump hangs - sometimes
    ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
    (freebsd-current)
  • RC1 dump hangs - sometimes
    ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
    (freebsd-current)