From owner-freebsd-fs Mon Mar 6 6:18:37 2000 Delivered-To: freebsd-fs@freebsd.org Received: from acutiator.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id 7294737BD67 for ; Mon, 6 Mar 2000 06:18:26 -0800 (PST) (envelope-from karsten@rohrbach.de) Received: from hardcore (dchp13.nacamar.de [195.63.63.246]) by acutiator.nacamar.de (Postfix) with SMTP id 126CD5D6F; Mon, 6 Mar 2000 15:17:43 +0100 (CET) Message-ID: <009701bf8776$b93963e0$f63f3fc3@hardcore> From: "Karsten W. Rohrbach" To: "Doug Rabson" Cc: "Mattias Pantzare" , "Edwin Mons" , =?iso-8859-1?Q?Administra=E7=E3o_MailBR?= , References: Subject: Re: NFS: Linux Client and BSD Server Date: Mon, 6 Mar 2000 15:02:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org so, if you mount -o nfsv3 and have vfs.nfs.async=1 it wont fail or does this mean that one has not to set vfs.nfs.async=1 ? /k -- The path of excess leads to the tower of wisdom. -W. Blake Karsten W. Rohrbach - Senior Research Engineer - Nacamar Data Communications one world. one net. nacamar - http://www.nacamar.net This was written on the road... Answers to your reply could be delayed. ----- Original Message ----- From: "Doug Rabson" To: "Karsten W. Rohrbach" Cc: "Mattias Pantzare" ; "Edwin Mons" ; "Administração MailBR" ; Sent: Monday, March 06, 2000 10:28 AM Subject: Re: NFS: Linux Client and BSD Server > On Mon, 6 Mar 2000, Karsten W. Rohrbach wrote: > > > Mattias Pantzare(pantzer@ludd.luth.se)@Thu, Jan 20, 2000 at 05:02:25PM +0100: > > > > When I did this while using an NFS (BSD <-> BSD) the speed went up to 1 > > > > MB/sec (on 10baseT). Theoretical maximum for 10 Mbit ethernet :-) > > > > > > And break the NFS protocol. Pray that the NFS server won't crash if you have > > > that on. > > > > what does vfs.nfs.async do, then, that it breaks the protocol? > > It replies to the RPC before the bits have actually hit stable storage. If > the server crashes or loses power before it syncs, the client has no way > of knowing that its data is lost. > > With NFSv3, there is a change to the protocol which allows most of the > performance of async but still allows the client to re-send its changes > after the server reboots. > > -- > 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-fs" in the body of the message