From owner-freebsd-questions Tue Jul 31 11:55: 8 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 0B22937B405 for ; Tue, 31 Jul 2001 11:55:02 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.4/8.11.4) id f6VIsx823261; Tue, 31 Jul 2001 13:54:59 -0500 (CDT) (envelope-from dan) Date: Tue, 31 Jul 2001 13:54:58 -0500 From: Dan Nelson To: Jay Sachs Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NFS v3 server locking fails Message-ID: <20010731135458.A890@dan.emsphone.com> References: <3B66D189.F8AF6763@eziba.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B66D189.F8AF6763@eziba.com> User-Agent: Mutt/1.3.20i X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jul 31), Jay Sachs said: > We're trying to get an Oracle db running on Solaris 2.6 to work with a > 4.3-Stable (7/24) system as the underlying filesystem via NFS. The > -Stable box has an ATA raid subsystem. The problem is that over NFS v3, > the Solaris system fails to acquire the lock, and NFSv2, though it > works, isn't really an option since it's (a) an order of magnitude > slower and more importantly, (b) we have files > 2gig. > > Are there any known problems with NFSv3 locking? If so, any know > workarounds? 4.* does not support locking over NFSv3 at all out of the box. I'm sending you patches that extend the dummy NFSv2 locking to NFSv3 in a separate message. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message