On Tue, 17 Jun 2003 10:30:32 +0100 "Clawson, Simon" simon_clawson@mentorg.com wrote:
What version of Linux? If its 7.3, then do a search on NOW for redhat 7.3+NFS. Its a known bug,a nd the RH Kernel needs upgrading to fix it properly.
All linux hosts run with linux kernel 2.4.18 - one with 2.4.19 (self compiled kernel). The distribution itself is a SuSE8.0.
-----Original Message----- From: Stefan Funke [mailto:bundy@arcor-ip.de] Sent: 17 June 2003 10:15 To: toasters@mathworks.com Subject: netdiag / linux nfs over tcp
Hi all!
Is someone having a lot of linux clients mounted a toaster via nfs over tcp? I have a mixed environment of linux, bsd and sunos clients. When I run "netdiag" here the toaster finds all linux hosts not to perform like they should:
Average size of NFS TCP packets received from host: foo is 461. This is less than the MTU (1500 bytes) of the interface involved in the data transfer. The maximum segment size being used by TCP for this host is: 1460. Low average size of packets received by this system might be because of a misconfigured client system, or a poorly written client application.
Is someone else seeing such output from netdiag?
I'm trying to locate a performance problem only appearing on linux hosts when the filer is under (heavy) load and a snapmirror proc from a second toaster is started. All linux clients produce a load up to 82 and start to freeze. Of course thats really not nice to have - especially when other bsd/sunos hosts have no problems.
Netapp itself can't help me - they say that the linux nfs drivers are a pieace of crap and that they're working with linux developers to fix that. (blah blah) Someone else ever had such problems? What did you do?