Description of Problem: file locking is blocking (hanging) on my nfs server. Version-Release number of selected component (if applicable): 0.3.1-13.7.2.1 How Reproducible: every time Steps to Reproduce: 1. exportfs client 2. mount host.. 3. run lock_test (see attachment: it hangs) Actual Results: locking a file on an nfs mounted file system hangs Expected Results: it should lock and then unlock Additional Information: the host filesystem is ext3 (converted from an ext2 original) -- perhaps this is the problem? my config used to work under rh 6.2 no problem. I'm also using NIS but I've replicated with this turned off, so it doesn't appear to be related to that. I've tried lots of variations for the exports file and the options in the fstab -- nothing seems to make a difference except of course specifying nolock in the fstab. here is my exports file on server neo: /usr grey(rw) /neo2 grey(rw) and df output: /dev/hda5 14555392 8129124 5686880 59% /usr /dev/hdb1 26312572 12107104 12868864 49% /neo2 and mount output: /dev/hda5 on /usr type ext3 (rw) /dev/hdb1 on /neo2 type ext3 (rw) here is my client fstab: neo:/usr /mnt/neo/usr nfs hard,intr,rw neo:/neo2 /mnt/neo/neo2 nfs hard,intr,rw locking fails on files within both mountpoints. I'm attaching output of rpcinfo -p, nfsstat, and a lock_test.c program to test, which I obtained from Havoc Pennington's post on the gnome.org archive mail list, which is concerning this very same problem that I'm having, but unfortunately does not provide any fixes: http://mail.gnome.org/archives/gconf-list/2001-October/msg00046.html kernel info for the host (and clients are the same): 74 neo:.../updates/7.2# uname -av Linux neo 2.4.9-7smp #1 SMP Thu Oct 18 13:34:30 EDT 2001 i686 unknown
Created attachment 41511 [details] C file that when compiled demonstrates blocking of locking
Created attachment 41512 [details] output of rpcinfo, nfsstat on host(neo) client(grey)
We believe this is fixed in the latest errata kernal. Can you try the 2.4.9-13 kernel and see if this fixes the problem?
Yep, kernel 2.4.9-13 fixes the problem -- thanks!