From owner-freebsd-current Tue Nov 17 08:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00566 for freebsd-current-outgoing; Tue, 17 Nov 1998 08:19:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00555 for ; Tue, 17 Nov 1998 08:19:26 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id RAA10676; Tue, 17 Nov 1998 17:22:48 +0100 (CET) Message-Id: <199811171622.RAA10676@rt2.synx.com> Date: Tue, 17 Nov 1998 17:17:46 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: Is it soup yet? FreeBSD NFS To: cejkar@dcse.fee.vutbr.cz cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199811131604.RAA08265@kazi.dcse.fee.vutbr.cz> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Nov, Cejka Rudolf wrote: > >> > Everyone seems to be talking about using FreeBSD as an NFS client, >> > how does FreeBSD do as a NFS server? >> > >> > -J >> > >> >> I'm going to be using NFS extensively at home for a while, I'll let you >> know. >> >> Last time I used it, it wasn't the most stable thing. A NFS mounted >> buildworld crashed the server once, but then worked fine after that. >> >> - -Alfred > > We have long-time problems (not critical) with NFS server running > on FreeBSD 2.2.6/2.2.7/3.0 against Solaris 2.5/2.6 clients there. > > Our problem: > > 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 > $ rm -r less-332 # This _still leaves_ 15 files! > rm: Unable to remove directory less-332: File exists > $ rm -r less-332 # Uff, directory is removed now... > > I think, problem is in different versions (NFSv2 vs. NFSv3) - but it > looks very trivial (?). If I mount NFS exported filesystem (exports > FreeBSD) on Solaris with option "vers=2" (it says "use NFSv2"), > problems disappear. But we are using cachefs (cached filesystem) over > NFS with automounting feature and we have no change to say "cachefs, > mount NFS filesystem with 'vers=2' option". There isn't any parameter > for this on Solaris... > > I have tried to use "mountd -2" on FreeBSD server part, but it > caused Solaris hangs... > > --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- > 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-current" in the body of the message I have an open problem on this (pr5890). Look at it and try the suggested fix. The machine where it is applied runs NFS serving for now 7 month and no problems appeared (clients: Solaris, aix, sco, hpux). No need to say that this needs a competent blessing....(re-read the BSD license before trying it :). RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message