On Dec 11, 2007, at 5:40 AM, Dave Howorth wrote:
Todd,
Thanks very much for your replies. They help enormously (not yet
enough
to say SOLVED, sadly) ...
Looks like you are on your way now though :)
M. Todd Smith wrote:
On Dec 7, 2007, at 3:49 PM, 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)
The default options since SuSe 9.x have been for TCP and NFSv3 by
default. It is still worth it to declare it in /etc/fstab for the
sake
of clarity.
Everything I've read about nfs says that v2 is the default, but I've
checked as you described and I'm seeing v3 as you say. Is that a
Suse-only thing?
Not that I am aware of, I checked the only other machine I have
running a 2.4.x kernel (2.4.20 redhat 9 machine). It too defaults to
nfsv3 connections on 4 different servers. I haven't seen a machine
default to nfsv2 for the past 4 years or so. You can do two things
really, get rid of the servers ability to serve up an NFSv2
connection, which I thought might have been happening on our SANS but
I setup a small NFS server to check it out and its still defaulting to
v3. This procedure is outlined in the NFS FAQ I link below. Or force
v3 on all your clients. I would probably force it all on the clients
as it is far more clear to see it in many /etc/fstab's then it is on a
single /etc/sysconfig file.
The client is where all the NFS mount options are asked for, so if
you
haven't changed it, then perhaps that should be the first place to
look
for the problem.
I don't understand this. I'm happy to go along but I don't understand.
I'd expect to look for problems in the place that *was* changed? But
here goes ...
The client asks the server for whatever options you give it. If the
server can comply then it will. Many people don't enforce nfsv3 or
tcp by default and thus it can easily be a point of contention. The
changed part is not always the problem piece, although I completely
agree with your logic :). Its certainly an odd behaviour, reminds me
of the days when you had to force 1000/full duplex connections because
the autonegotiation never seemed to work properly.
I think the FAQ at http://nfs.sourceforge.net/ may help you out a
little in the troubleshooting process of NFS.
Cheers
Todd
Systems Administrator
---------------------------------------------
Soho VFX - Visual Effects Studio
99 Atlantic Avenue, Suite 303
Toronto, Ontario, M6K 3J8
(416) 516-7863
http://www.sohovfx.com
---------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
