From owner-freebsd-stable Fri Feb 2 13: 8: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 67AE337B491 for ; Fri, 2 Feb 2001 13:07:41 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f12L7ej07515; Fri, 2 Feb 2001 13:07:40 -0800 (PST) Date: Fri, 2 Feb 2001 13:07:40 -0800 From: Alfred Perlstein To: Bill Moran Cc: stable@FreeBSD.ORG Subject: Re: NFS v3 broken? (or is it SGI's fault) Message-ID: <20010202130739.A26076@fw.wintelcom.net> References: <3A7B1D48.8FEC89F0@mail.iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A7B1D48.8FEC89F0@mail.iowna.com>; from wmoran@mail.iowna.com on Fri, Feb 02, 2001 at 03:49:12PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bill Moran [010202 12:53] wrote: > Anyone else seen this? > NFS connnection from and SGI box(client) to a FreeBSD box (server) will > fail when writing if the connection is done using v3 of NFS. > Using v2 works just dandy. Other operations seem to work just fine under > v3 (change perms, scan directories, read files) > > Bug? SGI's fault? If more debugging info would be helpful I can provide > it. Just let me know how to get what you need. > > This is using 4.2-STABLE from Jan 8. Our lockd doesn't support NFSv3 locks, it's been on my TODO list for over a year to bring in the patch to do it, just never had the time. If you search the archives, look for Dan Nelson, he's got the patch I did. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message