You'll need to read my reply using the (1), (2), (3) sequence for it to make sense :) Sorry, it was easier than cutting and pasting bits Dave Howorth wrote:
Rui Santos wrote:
Dave Howorth wrote:
I have a server that's been running fine for some years with Suse 9.2. I've just installed 10.3 and am now getting 'File size limit exceeded' errors.
The access is being made by an application on another box, running 9.2. It's trying to copy a 2.7 GB file from a local disk to a filesystem on the server that it's mounting using NFS. The filesystem is reiserfs and was not changed when I upgraded the OS. Both machines are 64-bit. The application has worked fine for years but now says:
File size limit exceeded
I don't have a file size limit (file size (blocks, -f) unlimited)
Google showed it may be a restriction of NFS V2 though why that is now running is another mystery. rpcinfo and nfsstat shows that server and client are both running both v2 and v3. I haven't been able so far to find out which version is in use for a particular mount. How can I do that?
Does anybody recognize these symptoms?
Yes,
You are probably establishing a NFSv2 connection.
That's what I'm guessing as well. I want to find out what versions all the connections are using to confirm that, but I don't know how.
(3) I still haven't found any way to discover what NFS version particular mounts are using.
The workaround I used to solve the problem was to instruct the server not to accept NFSv1 nor NFSv2 connections.
(2) The script /etc/init.d/nfsserver was completely rewritten between 9.2 and 10.3. In 9.2 it started rpc.mountd like this: startproc /usr/sbin/rpc.mountd while in 10.3 it starts it like this: echo "+2 +3 -4" > /proc/fs/nfsd/versions VERSION_PARAMS="--no-nfs-version 4" ... startproc /usr/sbin/rpc.mountd $VERSION_PARAMS I don't know whether that would be enough to change the default behaviour. But there doesn't seem to be any provision to change the options that rpc.mountd is started with. Did you hack the script?
That's what I think I'd like to do, but I need to discover what all the existing mounts are and find out why any V2 ones are V2 and whether they need to be before I can turn off V2 mount support.
But, you can try to force a specific version on the mount command from the client side by giving the parameter 'nfsvers=3'. eg: mount -t nfs -o defaults,nfsvers=3 nfsserver:/share /mountpoint
(1) I've now done this as you and Hans suggested and it has fixed the problem. So I think that confirms that the Suse10.3 server is making NFSv2 connections by default whereas the Suse9.2 server made NFSv3 connections. I still don't understand why, though. See above
Thanks, I'll try that to at least see if I can fix the specific issue I have with this particular application.
Cheers, Dave
If it works, you can then instruct the server not to accept NFSv1/2 connections, if it suits your needs, of course.
Thanks, Dave
Hope it helps, Rui
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org