From owner-freebsd-current Wed Aug 25 0:42:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CC6FB153F0 for ; Wed, 25 Aug 1999 00:42:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA10533; Wed, 25 Aug 1999 08:52:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 25 Aug 1999 08:52:40 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: "David O'Brien" , current@freebsd.org, vladimir@math.uic.edu Subject: Re: NFSv3 on freebsd<-->solaris In-Reply-To: <199908240344.UAA12309@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, Matthew Dillon wrote: > :... > :am not implying that the problem might be on the FreeBSD side, it might > :as well be a bug in solaris NFS implementation). > : > :I would greatly appreciate any help with the following problem. I have > :a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 > :client. I run into problems when trying to use NFSv3 mounts on the > :client. Trying to remove files from the mounted partition (on the nfs > :client) results in multiple errors, for example: > : > : # rm -r /home/2/vladimir > : rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists > : rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists > : rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists > : > :I have tried using tcp and udp mount options with the same result. NFSv2 > :works fine. > : > :Solaris client has the latest patches applied. I would very much appreciate > :any comments on that. > > When you look at those directories on the server from the server are there any > files left over? > > If so then the rm -r is somehow missing some files and then is unable to > rmdir the directory because it isn't yet empty. This is probably because our server detects that the directory has been modified and rejects the solaris client's directory cookies. Instead of recovering, the solaris client barfs. Its a solaris bug really but perhaps we can add a knob to relax our directory modified checks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message