From owner-freebsd-hackers Wed Nov 18 13:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09854 for freebsd-hackers-outgoing; Wed, 18 Nov 1998 13:27:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09849 for ; Wed, 18 Nov 1998 13:27:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA12041; Wed, 18 Nov 1998 16:27:24 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id QAA02754; Wed, 18 Nov 1998 16:27:26 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Wed, 18 Nov 1998 16:27:26 -0500 From: "David E. Cross" To: Conrad Minshall cc: Cejka Rudolf , freebsd-hackers@FreeBSD.ORG Subject: Re: Is it soup yet? FreeBSD NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Conrad Minshall wrote: > >> On 13 Nov, Cejka Rudolf wrote: > > >> > FreeBSD: NFS server without any special parameters. > >> > Solaris: NFS client without any special parameters. > >> > > >> > Example - working on Solaris above mounted filesystem from FreeBSD: > >> > > >> > $ gzcat less-332.tar.gz | tar xvf - # This creates 74 files in > >> > # directory less-332 > >> > $ rm -r less-332 # This _leaves_ 43 files! > >> > rm: Unable to remove directory less-332: File exists > > Do the 43 file names left behind start with ".nfs" or are they the original > filenames created by the "tar xvf -"? Been there, done that. This happens to me all the time if this is a NFSv3 mount (which is what Solaris will default to). I remember once long ago when we were first doing v3 there where some issues about filehandles for directories, I remember this being one of the side-effects of that problem. I don't remember if that was ever resolved. short term fix: use NFSv2 (mount -o vers=2 freebsd.server:/path /local/path) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message