Date: Wed, 25 May 2005 18:45:26 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Viren Patel <virenp@mail.utexas.edu> Cc: freebsd-questions@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: NFS broken after upgrading to 5.4 Message-ID: <20050526014526.GA7378@xor.obsecurity.org> In-Reply-To: <1475.66.25.129.27.1117071597.squirrel@mail.cm.utexas.edu> References: <1282.66.25.129.27.1117067480.squirrel@mail.cm.utexas.edu> <20050526010713.GA92954@xor.obsecurity.org> <1475.66.25.129.27.1117071597.squirrel@mail.cm.utexas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 25, 2005 at 08:39:57PM -0500, Viren Patel wrote: > > On Wed, May 25, 2005 at 07:31:20PM -0500, Viren Patel > > wrote: > >> Hello all. I have several FreeBSD clients connecting to > >> a > >> FreeBSD NFS server via a private gigabit LAN for backup > >> purposes. Both clients and server has IPFW with all > >> traffic between clients and server allowed on the > >> private > >> LAN. All clients and the server were running > >> 5.3-RELEASE-p10 with IPFW, and NFS was working just > >> fine. > >> Then I upgraded all clients to 5.4-RELEASE-p1 and the > >> NFS > >> was working fine. Finally I upgraded the NFS server to > >> 5.4-RELEASE-p1 and now NFS has stopped working. The > >> clients experience RPC timeouts: > >> > >> RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > >> > >> My NFS server rc.conf has the following as per manual: > >> > >> nfs_server_enable=3D"YES" > >> rpcbind_enable=3D"YES" > >> mountd_flags=3D"-r" > >> > >> Clients have: > >> > >> nfs_client_enable=3D"YES" > >> > >> IPFW rules amount to: > >> > >> allow all from NFS_SERVER to NFS_CLIENT in via > >> INTERNAL_IF > >> allow all from NFS_CLIENT to NFS_SERVER out via > >> INTERNAL_IF > >> > >> and appear at the top of the ruleset. > > > > Double check this, then triple-check it, because a local > > configuration > > difference like this is likely to be your cause. > > > >> Obviously something has changed in the NFS system under > >> 5.4 > > > > Not that I can think of. > > > > Kris > > >=20 > I have checked my configuration multiple times. Nothing > there has changed between 5.3 and 5.4. I have even > disabled the firewalls on both clients and server but the > same problem is present. >=20 > Another interesting behavior: upon reboot, mount_nfs > occasionally succeeds. However if I then go to another > client and try to access the NFS server it doesn't work. > If I then go back to the first client and try to unmount > the NFS partition it also hangs. What does ^T show for the status of the 'hung' process? Are you certain that DNS resolution is working correctly on both machines? Kris --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFClSo2Wry0BWjoQKURAsxBAKCdsijpGwJ1IJnfFrrshgf+ttb5wQCfUhRB Ciwd1xzOuzf8qH9y6ICGtsE= =sGm8 -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050526014526.GA7378>