nfs client bug?

Steven N. Hirsch (shirsch@ibm.net)
Sun, 15 Mar 1998 18:08:56 -0500 (EST)


Bill,

Haven't seen any postings from you for a while! Hopefully, you are still
engaged in kernel hacking <g>.

I've isolated an apparent incompatibility between the current nfs client
(2.1.90p3) and my trusty old IBM RT. The RT (predecessor to the RS/6000,
sort of..) runs BSD 4.3. I hadn't fired it up in a while; since before I
migrated to 2.1.x on all my machines. Today, after chasing what I thought
were configuration problems on the server, I discovered that the current
client has some problems:

Mar 15 14:07:16 air kernel: RPC: xprt_create_proto called
Mar 15 14:07:16 air kernel: RPC: xprt_create_socket(c0a8f43c, udp 17)
Mar 15 14:07:16 air kernel: RPC: setting up UDP transport...
Mar 15 14:07:16 air kernel: RPC: created transport c1b92000
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_reserve cong = 0 cwnd = 256
Mar 15 14:07:16 air kernel: RPC: 38267 reserved req c1b9206c xid 00009fee
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_reserve returns 0
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_transmit(9fee)
Mar 15 14:07:16 air kernel: RPC: xprt_sendmsg(160) = 160
Mar 15 14:07:16 air kernel: RPC: 38267 xmit complete
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive returns 0
Mar 15 14:07:16 air kernel: RPC: udp_data_ready...
Mar 15 14:07:16 air kernel: RPC: udp_data_ready client c1b92000
Mar 15 14:07:16 air kernel: RPC: 38267 received reply
Mar 15 14:07:16 air kernel: RPC: cong 00000100, cwnd was 00000100, now 00000200, time 8000 ms
Mar 15 14:07:16 air kernel: RPC: 38267 has input (20 bytes)
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_transmit(9fee)
Mar 15 14:07:16 air kernel: RPC: xprt_sendmsg(160) = 160
Mar 15 14:07:16 air kernel: RPC: 38267 xmit complete
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive returns 0
Mar 15 14:07:16 air kernel: RPC: udp_data_ready...
Mar 15 14:07:16 air kernel: RPC: udp_data_ready client c1b92000
Mar 15 14:07:16 air kernel: RPC: 38267 received reply
Mar 15 14:07:16 air kernel: RPC: 38267 has input (20 bytes)
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_transmit(9fee)
Mar 15 14:07:16 air kernel: RPC: xprt_sendmsg(160) = 160
Mar 15 14:07:16 air kernel: RPC: 38267 xmit complete
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive
Mar 15 14:07:16 air kernel: RPC: 38267 xprt_receive returns 0
Mar 15 14:07:16 air kernel: RPC: udp_data_ready...
Mar 15 14:07:16 air kernel: RPC: udp_data_ready client c1b92000
Mar 15 14:07:16 air kernel: RPC: 38267 received reply
Mar 15 14:07:16 air kernel: RPC: 38267 has input (20 bytes)
Mar 15 14:07:16 air kernel: RPC: 38267 release request c1b9206c
Mar 15 14:07:16 air kernel: nfs_read_super: get root fattr failed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^6
Mar 15 14:07:16 air kernel: RPC: destroying transport c1b92000

This was after setting all the things under /proc/sys/sunrpc to "1".. I
do hear some disk activity on the server with each (failed) mount attempt,
but nothing appears on its logs.

As a control, I built 2.0.34p3 and rebooted. All works correctly, so it
wasn't my imagination.

What would you like me to try in order to nail down this problem?

Steve

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu