Date: Sun, 11 May 1997 15:10:09 -0300 (EST) From: Joao Carlos Mendes Luis <jonny@mailhost.coppe.ufrj.br> To: fs@freebsd.org Subject: NFS between 2.2.1 and 2.1.7.1 Message-ID: <199705111810.PAA09593@gaia.coppe.ufrj.br>
next in thread | raw e-mail | index | archive | help
Hi,
I've recently upgraded some of my NFS clients from FreeBSD 2.1.7 to
FreeBSD 2.2.1-R. The server is too important to risc an upgrade right
now. Also, on both systems I also upgraded from ethernet 10M (ne2000
and DEC 21040) to ethernet 100M (3c905). The hardware change some weeks
after upgrading the OS version.
Since the hardware upgrade, the client machine seens to be extremely
problematic about NFS. It's always blocking NFS calls, and I don't
know why. Here's some info:
Client:
zeus::root [541] ps -alx | grep nfs
0 109 1 0 2 0 232 12 accept Is ?? 0:00.01 nfsd: master
0 111 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server
0 112 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server
0 113 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server
0 114 109 0 2 0 224 12 nfsd I ?? 0:00.02 nfsd: server
0 124 1 0 2 0 208 12 sbwait D ?? 0:00.18 nfsiod -n 4
0 125 1 0 -1 0 208 12 nfsrcv D ?? 0:00.07 nfsiod -n 4
0 126 1 0 -1 0 208 12 nfsrcv D ?? 0:00.01 nfsiod -n 4
0 127 1 0 -1 0 208 12 nfsrcv I ?? 0:00.01 nfsiod -n c
100 4955 4937 7 -1 0 2136 2576 nfsrcv I p2 0:03.03 sdr
100 4918 1 0 -1 0 220 772 nfsrcv I v0 0:00.13 xbiff
100 4951 1 0 -1 0 6768 2776 nfsrcv D v0 0:06.19 /usr/local/l
Server:
gaia::jonny [328] ps -alx | grep nfs
0 185 1 0 2 0 324 40 netcon Is ?? 0:00.02 nfsd: master
0 187 185 0 2 0 316 12 nfsd I ?? 0:00.00 nfsd: server
0 188 185 0 2 0 316 12 nfsd S ?? 0:08.28 nfsd: server
0 189 185 0 2 0 316 12 nfsd I ?? 0:00.13 nfsd: server
0 190 185 0 2 0 316 12 nfsd I ?? 0:00.01 nfsd: server
0 194 1 0 10 0 208 12 nfsidl I ?? 0:01.07 nfsiod -n 4
0 195 1 0 10 0 208 12 nfsidl I ?? 0:00.07 nfsiod -n 4
0 196 1 0 10 0 208 12 nfsidl I ?? 0:00.34 nfsiod -n 4
0 197 1 0 10 0 208 12 nfsidl I ?? 0:00.08 nfsiod -n 4
The client seems to be locked at the "nfsrcv" resource, when it should be
at "nfsidl". It's not a network problem (at least, not a permanent one),
since I can still telnet or everywhere.
I shall try to change the nics and maybe the network cable (it's not
a very good one), but this really looks like a software problem.
Jonny
--
Joao Carlos Mendes Luis jonny@gta.ufrj.br
+55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br
Network Manager UFRJ/COPPE/CISI
Universidade Federal do Rio de Janeiro
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705111810.PAA09593>