Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 May 2005 08:17:48 -0500
From:      Skylar Thompson <skylar@cs.earlham.edu>
To:        freebsd-stable@freebsd.org, freebsd-questions@freebsd.org
Subject:   Weird NFS problems
Message-ID:  <4295CC7C.3080009@cs.earlham.edu>

next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2590F6538AA160E8679A44C8
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm having some problems with NFS serving on a FreeBSD 5.4-RELEASE 
machine. The FreeBSD machine is the NFS/NIS server for a group of four 
Linux clusters. The network archictecture looks like this:

234/24                                                   234/24
Cluster 1 ---                    |--------------- Cluster 3
                   | ---------------
            em0|  File server | fxp0
                   |  --------------
Cluster 2 ---                    |--------------- Cluster 4
234/24                                                    230/24


em0 and fxp0 are bridged, and em0 has a 234/24 IP address while fxp0 is 
just in promiscuous mode. 234/24 is an 802.1q VLAN on the fxp0 side of 
the server, so packets are untagged at the switch just before fxp0, and 
are forwarded to em0 through the bridge.

The problem manifests itself in large UDP NFS requests from Clusters 3 
and 4. The export can be mounted fine from both those clusters, and 
small transfers such as with ls work fine, but the moment any serious 
data transfer starts, the entire mount just hangs. Running ethereal on 
the file server shows a a lot of fragmented packets, and RPC 
retransmissions on just a single request. Reducing the read and write 
NFS buffers on the Linux clients to 1kB from the default of 4kB solves 
the issue, but kills the transfer rate. The moment I go to 2kB, the 
problem reappearss. Clusters 1 and 2 use the default of 4kB buffers, and 
have no problems communicating to em0.

Poking through the list archives, I ran across this message 
(http://lists.freebsd.org/pipermail/freebsd-stable/2003-May/001007.html) 
that reveals a bug in the fxp(4) driver in 4-RELEASE that incorrectly 
detects the capabilities of the NIC. Is this still an issue in 
5-RELEASE, or am I looking at a different problem? Any ideas on how I 
can get the NFS buffers up to a reasonable level?

-- 
-- Skylar Thompson (skylar@cs.earlham.edu)
-- http://www.cs.earlham.edu/~skylar/


--------------enig2590F6538AA160E8679A44C8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFClcx+sc4yyULgN4YRAi7fAJ9ab6DUOFphaC5VGyApxiJNGqHhfgCgoXdq
/6pI9l13DbYeaMUuUKlgvNU=
=v9JM
-----END PGP SIGNATURE-----

--------------enig2590F6538AA160E8679A44C8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4295CC7C.3080009>