Comment 16 for bug 581941

I have been having this same issue I have just upgrade from 8.10 to 10.04 over a three week period . When I first upgrade all our mac 10.6 and 10.5 clients stopped auto mounting nfs homes and I used another bug (#540637) report which fixed the issue up untill 3 days ago when I started to have client not able to mount their home dir. after stopping nfs-kernel-server and portmap and restarting then they could mount their home folders but they keeped getting kick off and losing the mount the only way I have been able to fix it is by running rpc.statd -Fd in a termal as root and their mount comes back . .

this is the log from this morning when we tried to log in
Aug 31 09:48:04 server kernel: [85461.640021] statd: server rpc.statd not responding, timed out
Aug 31 09:48:34 server kernel: [85491.640026] statd: server rpc.statd not responding, timed out
Aug 31 09:49:04 server kernel: [85521.642522] statd: server rpc.statd not responding, timed out
Aug 31 09:49:34 server kernel: [85551.641267] statd: server rpc.statd not responding, timed out
Aug 31 09:50:04 server kernel: [85581.640030] statd: server rpc.statd not responding, timed out
Aug 31 09:50:34 server kernel: [85611.642517] statd: server rpc.statd not responding, timed out
Aug 31 09:51:04 server kernel: [85641.642517] statd: server rpc.statd not responding, timed out
Aug 31 09:51:34 server kernel: [85671.640017] statd: server rpc.statd not responding, timed out
Aug 31 09:52:04 server kernel: [85701.640023] statd: server rpc.statd not responding, timed out
Aug 31 09:52:34 server kernel: [85731.640017] statd: server rpc.statd not responding, timed out
Aug 31 09:53:04 server kernel: [85761.640022] statd: server rpc.statd not responding, timed out
Aug 31 09:53:34 server kernel: [85791.640016] statd: server rpc.statd not responding, timed out
Aug 31 09:54:04 server kernel: [85821.640034] statd: server rpc.statd not responding, timed out
Aug 31 09:54:34 server kernel: [85851.640027] statd: server rpc.statd not responding, timed out
 rpc.statd[21644]: segfault at 2011 ip 00007fce39966cba sp 00007fffdecdb740 error 4 in libc-2.11.1.so[7fce39853000+17a000]
Aug 31 10:11:35 server kernel: [86872.690017] statd: server rpc.statd not responding, timed out
Aug 31 10:12:45 server kernel: [86942.606646] rpc.statd[21887]: segfault at 2011 ip 00007f6a45831cba sp 00007fff75c4b9c0 error 4 in libc-2.11.1.so[7f6a4571e000+17a000]
Aug 31 10:13:15 server kernel: [86972.630014] statd: server rpc.statd not responding, timed out
Aug 31 10:13:47 server kernel: [87005.004577] rpc.statd[22381]: segfault at 2011 ip 00007f9568963cba sp 00007fff82db1e90 error 4 in libc-2.11.1.so[7f9568850000+17a000]
Aug 31 10:16:47 server kernel: [87185.006961] rpc.statd[22455]: segfault at 2011 ip 00007fdcda8f1cba sp 00007fffb7995ba0 error 4 in libc-2.11.1.so[7fdcda7de000+17a000]

after stopping nfs and portmap and restarting portmap then nfs I could log in and mount home folder but every 30 to 60 min every one loses their home folder till i run rpc.statd -Fd in termal .

has and one got any ideas on how to fix this.