It appears that the NFS client still has a few problems in 2.1. In the
case above it's just a performance issue, but I had worse experiences
with an Intel box running 2.1.100+ and NFS, mounting shares from a Solaris
2.5.1 server.
Simply put, if the share is mounted using NFSv3/TCP, writing over NFS is
completely broken. The kernel starts complaining loud (I forgot what the
message is, but I can redo the tests if anybody is interested), and nothing
or very little actually makes it to the server. The file gets created, but
that's about it. All the other parameters are the default ones, i.e. rsize=
wsize=1024.
Snooping on the wire with tcpdump shows lots of very short lived TCP
connections between the client and the server. Isn't the clients supposed
to maintain one open connection w/ the server when using TCP? Anyway,
again, if somebody is interested, I can provide the dumps.
One last point: "normal" (i.e. NFSv2/UDP) mounts seems to be fine on
Intel. I can't comment on the performance though.
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu