From owner-freebsd-hackers Thu Nov 19 02:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10732 for freebsd-hackers-outgoing; Thu, 19 Nov 1998 02:06:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10672 for ; Thu, 19 Nov 1998 02:05:55 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id LAA05589; Thu, 19 Nov 1998 11:04:58 +0100 (CET) Received: from alzbeta.dcse.fee.vutbr.cz (alzbeta.dcse.fee.vutbr.cz [147.229.8.62]) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) with ESMTP id LAA01963; Thu, 19 Nov 1998 11:04:57 +0100 (CET) Received: (from cejkar@localhost) by alzbeta.dcse.fee.vutbr.cz (8.8.8+Sun/8.8.8) id LAA08125; Thu, 19 Nov 1998 11:04:55 +0100 (MET) From: Cejka Rudolf Message-Id: <199811191004.LAA08125@alzbeta.dcse.fee.vutbr.cz> Subject: Re: Is it soup yet? FreeBSD NFS In-Reply-To: from "David E. Cross" at "Nov 18, 98 04:27:26 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Thu, 19 Nov 1998 11:04:54 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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) In many cases this fix is sufficient. But as I said: We are using cachefs with automounting feature there. Cachefs mounts underlying filesystem (NFS in our case) automatically and I haven't found any parameter for changing behaviour of NFS mounting. For example there is cachefs config line: /where -fstype=cachefs,cachedir=/xxx/cache,backfstype=nfs server:/from All parameters are going to cachefs, not nfs :-(. "vers=2" doesn't work, "backfsoptions" doesn't exist... Disabling cachefs (or automounting feature) is worse than living with "rm -r something" bug for us. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message