It seems Matt wrote: > I'm now running a kernel/world of October 26th on both NFS client and > server machines. I am still seeing NFS lockups as reported by several > people in these threads: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1296172+0+archive/2003/freebsd-current/20031026.freebsd-current > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1333116+0+archive/2003/freebsd-current/20031026.freebsd-current > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1477462+0+archive/2003/freebsd-current/20031026.freebsd-current > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1469939+0+archive/2003/freebsd-current/20031026.freebsd-current > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1467159+0+archive/2003/freebsd-current/20031026.freebsd-current > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1314547+0+archive/2003/freebsd-current/20031026.freebsd-current > > I just tried port upgrading bind9 and it got 10% through downloading and > locked up. I tried an ls /usr/ports and there was no response. I had to > umount -f /usr/ports to get the processes to exit. > > Poul-Henning's patch did not have any effect because it appears to be > the client at fault not the server as Marc Olzheim mentioned that he has > the same issue with a 4.x NFS server machine using a 5.1-current client.
Me too!! -Søren _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
