Date: Mon, 6 Mar 2000 09:28:11 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: "Karsten W. Rohrbach" <karsten@rohrbach.de> Cc: Mattias Pantzare <pantzer@ludd.luth.se>, Edwin Mons <e.mons@spcgroup.nl>, =?iso-8859-1?Q?Administra=E7=E3o_MailBR?= <mailbr@mailbr.com.br>, freebsd-fs@freebsd.org Subject: Re: NFS: Linux Client and BSD Server Message-ID: <Pine.BSF.4.21.0003060926400.8714-100000@salmon.nlsystems.com> In-Reply-To: <20000306064734.A61425@rohrbach.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003060926400.8714-100000>