From owner-freebsd-stable Mon Jun 28 16:48:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 96A4A1520F for ; Mon, 28 Jun 1999 16:47:52 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id BAA07835; Tue, 29 Jun 1999 01:47:31 +0200 (MET DST) Date: Tue, 29 Jun 1999 01:47:29 +0200 (MET DST) From: Gerald Pfeifer To: stable@freebsd.org Cc: obrien@nuxi.com Subject: Re: NFSv3 seriously broken in 3.1 In-Reply-To: <19990428154346.A77100@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, David O'Brien wrote: >> With this setup, I experience serious NFS problems, unless I explicitely >> set "opts:=nfsv2" in all AMD maps. > ... >> Has there been any change to fix this on -STABLE after 3.1? > As I've said, the default is v3/UDP. In previous postings that seemed to > make everybody happy. I'll review my mail archive and verify that. Just to make sure, there has been no change between FreeBSD 3.1 and 3.2, right? We have some new FreeBSD 3.2 boxes and experience strange hangs when sending mail from Pine ("Sending 0%" forever), which are exactly the symptoms we had on FreeBSD 3.1 until I fixed "opts:=nfsv2" in all AMD maps. This is rather annoying and I feel a bit lost, for this never occurs on FreeBSD 3.1 with exactly the same AMD map. Have there been any changes concerning direct mounts via fstab? /var/mail is mounted like that. Respectively, I believe someone mentioned a way to "lock" an entire host to NFS 2, so that specifying this in individual AMD maps is not needed any more, but failed to find _where_ to configure that. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message