OK, I turned on debug with: echo "65535" > /proc/sys/sunrpc/nlm_debug
There seems to be a problem when lockd enters garbage collection. Here's the last of the debug seen from lockd on the server side. [ 2277.091005] lockd: request from 192.168.1.210, port=864 [ 2277.091018] lockd: LOCK called [ 2277.091022] lockd: nlm_lookup_host(192.168.1.210, p=6, v=4, my role=server, name=romita) [ 2277.091026] lockd: get host romita [ 2277.091027] lockd: nsm_monitor(romita) [ 2277.091031] lockd: nlm_file_lookup (01070001 00288001 00000000 926e57da d142d9c6 dabb48bd c2a30bcf 0028c75d) [ 2277.091035] lockd: creating file for (01070001 00288001 00000000 926e57da d142d9c6 dabb48bd c2a30bcf 0028c75d) [ 2277.091047] lockd: found file f7be3900 (count 0) [ 2277.091050] lockd: nlmsvc_lock(sda1/2672477, ty=0, pi=58832, 1073741824-1073741824, bl=0) [ 2277.091054] lockd: nlmsvc_lookup_block f=f7be3900 pd=58832 1073741824-1073741824 ty=0 [ 2277.091056] lockd: nlm_lookup_host(192.168.1.210, p=6, v=4, my role=server, name=romita) [ 2277.091058] lockd: get host romita [ 2277.091062] lockd: created block ecbfe6c0... [ 2277.091066] lockd: vfs_lock_file returned 0 [ 2277.091068] lockd: freeing block ecbfe6c0... [ 2277.091069] lockd: release host romita [ 2277.091071] lockd: nlm_release_file(f7be3900, ct = 2) [ 2277.091073] lockd: nlmsvc_lock returned 0 [ 2277.091075] lockd: LOCK status 0 [ 2277.091076] lockd: release host romita [ 2277.091078] lockd: nlm_release_file(f7be3900, ct = 1) [ 2277.091298] lockd: request from 192.168.1.210, port=864 [ 2277.091302] lockd: LOCK called [ 2277.091304] lockd: nlm_lookup_host(192.168.1.210, p=6, v=4, my role=server, name=romita) [ 2277.091306] lockd: get host romita [ 2277.091307] lockd: nsm_monitor(romita) [ 2277.091310] lockd: nlm_file_lookup (01070001 00288001 00000000 926e57da d142d9c6 dabb48bd c2a30bcf 0028c75d) [ 2277.091316] lockd: found file f7be3900 (count 0) [ 2277.091319] lockd: nlmsvc_lock(sda1/2672477, ty=0, pi=58832, 1073741826-1073742335, bl=0) [ 2277.091322] lockd: nlmsvc_lookup_block f=f7be3900 pd=58832 1073741826-1073742335 ty=0 [ 2277.091325] lockd: nlm_lookup_host(192.168.1.210, p=6, v=4, my role=server, name=romita) [ 2277.091327] lockd: host garbage collection [ 2277.091328] lockd: nlmsvc_mark_resources Nothing more is seen from the lockd after the start of the GC. Looking at earlier GC runs from the syslog, the pattern is: [ 2037.388911] lockd: nlm_lookup_host(192.168.1.210, p=6, v=4, my role=server, name=romita) [ 2037.388914] lockd: host garbage collection [ 2037.388916] lockd: nlmsvc_mark_resources [ 2037.388920] nlm_gc_hosts skipping romita (cnt 0 use 0 exp 455264) [ 2037.388922] nlm_gc_hosts skipping ditko (cnt 0 use 0 exp 460016) [ 2037.388924] lockd: get host romita So it finds a couple of entries (skips 'em) and then breaks out to carry on immediately with "get host". I'm assuming that GC is invoked as part of lookup handling, and doesn't just get triggered asynchronously. Anyhow, this looks like a good spot to start digging. I don't see anything running on top (does lockd show on top?) But the process still seems to be in the ps table. It just doesn't do anything any more. [EMAIL PROTECTED]:/boot/grub# ps -ef|grep lockd root 4715 2 0 14:19 ? 00:00:00 [lockd] [EMAIL PROTECTED]:/boot/grub# top Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st [EMAIL PROTECTED]:/boot/grub# uname -a Linux kirby 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux Machine is a dual-core Intel on a Shuttle board. Hard disk is SATA. -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
