Dave Howorth wrote:
On Fri, 2007-12-07 at 15:34 +0100, Hans Witvliet wrote:
For larger files, you can not use the default mount options anymore!
You must use nfsvers=3 instead on nfsver=2 (and use tcp instead of udp)
Hi Hans, Thanks for this. I will try it on Monday. But again, *this has
been working for years.* I've been copying a file > 2 GB every two weeks
for years, successfully, without using this option. It has only now
stopped working AFTER I installed 10.3 on the server. I haven't changed
the client - where the mount request is made.
Something has broken backwards compatibility and I'd like to discover
what.
---
The name of the nfs clients and server packages were renamed
in 10.3 -- that's the first different (that shouldn't make a difference).
The next thing -- as near as I can tell, 10.3 defaults to NFS4. At
least this was what I found out when I ran into the same problems in
10.3. I "upgraded" the packages to the working nfs packages in 10.2
and things went back to normal and started working.
Also -- in trying to upgrade, somehow I picked the wrong
NFS-server somewhere for one of my servers -- it started serving with
a user-space NFS-server instead of the kernel-NFS server. The user
space NFS-server I had been using, also seemed to have a 2GB limit
as well as being limited to NFSv2.
Am now running with NFSv3 and thinks seem to work -- I did
have to "backgrade" the needed NFS-related files to suse10.2, though,
to make it work.
NFSv4 also seems to need another daemon or two -- some sort of
id mapper, at least. Might be useful in some environments, but until I
complete upgrades on my machines, I am sticking with SuSE10.2's NFS
images as they just "worked" for me.
Good luck,
Linda
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
