[Bug 578866] [NEW] NFS4 kills system (no reboot possible)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have migrated from a NFS3 infrastructure to NFS4 (without kerberos)
(to workaround  #525154)

Setup:
* ubuntu/lucid amd64
   autofs5/lucid uptodate 5.0.4-3.1ubuntu5
   linux-image-generic/lucid uptodate 2.6.32.22.23 [because I have got troubles to boot the system with a -server kernel (since lucid) I'm using currently the -generic kernel]
   nfs-kernel-server/lucid uptodate 1:1.2.0-4ubuntu4
* create /srv/nfs4 and export it via NFS4
* have bind mounts from /srv/nfs4 to the traditional mount points of the exported shares

With NFS4 I can't use bind mount with autofs (out of the box).
So I have to access "shared" drives locally also with NFS4.

If I copy a big file (e.g. a CD image) to a share mounted via NFS4 locally after short time the system is blocked.
* LoadAvg grows to infinity 
* After some time I see messages about blocked task correlated to nfs or accessing nfs shares on the local sever and all clients accessing this server
* shutdown/reboot will also blocked and not come to an end
  To reboot the system I have to issue a hard reboot on the server console

The problem doesn't occur if I:
* copy only smaller files
* copy files from client to the server (e.g. a 160GB hdd image was processed without error)

The problem occurs on both nfs servers.

Hardware:
2 similar boxes with:
* TYAN Thunder  K8WE S2895
* 2 Opteron K8 CPUs
* SCSI and SATA hdds


[As a workaround I will create diverted autofs configuration with explicit local binding mounts.]

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
NFS4 kills system (no reboot possible)
https://bugs.launchpad.net/bugs/578866
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux in ubuntu.