Vlad Glagolev wrote:
Hmm, more testing.. It works only with tiny files flawlessly on OpenBSD (client). If a filesize is around 50 mibs, then it just freezes and eats cpu with nfsrcvl call. On Linux I don't see such problem. Even big files are transfered with good enough speed.
I think that is a second problem. There are simple ways to screw up the fsid's and produce stale fs warnings...so I was guessing it might be a slightly different variation of the one I had seen before were we were getting through some series of commands different exported fs with the same fsid and the client machine basically had the fs switched out from under it...
You might try different nfsvers(may work, but ver 2 has some issues displaying the proper sizes on >2tb fs, and has 1-2tb file limits--I believe) on the mounts on bsd, and or different wsize/rsize(unlikely to help) and such...but I am not sure it will necessarily matter, but one may cause less issues from with one set of options vs another as each is likely a fairly different code path, and the same with trying the proto tcp vs udp changes quite a bit of code out...
You can on most oses check what options were actually accepted on the mount on linux it is a cat /proc/mounts the mount command may do it on bsd...but that will tell you if it accepted the specified options or ignored them.
-- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
