From owner-freebsd-questions Wed Jun 12 15:41:46 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10694 for questions-outgoing; Wed, 12 Jun 1996 15:41:46 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA10687 for ; Wed, 12 Jun 1996 15:41:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA07001; Wed, 12 Jun 1996 15:39:53 -0700 From: Terry Lambert Message-Id: <199606122239.PAA07001@phaeton.artisoft.com> Subject: Re: Fast SCSI controller To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Wed, 12 Jun 1996 15:39:53 -0700 (MST) Cc: dwhite@riley-net170-164.uoregon.edu, freebsd-questions@FreeBSD.org In-Reply-To: <199606122110.RAA00457@crh.cl.msu.edu> from "Charles Henrich" at Jun 12, 96 05:10:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > One thing no one has mentioned is that NFS on FreeBSD is pretty horrid. On > 2.1R I get lockups on the client quite a bit, in the server mode I've seen it > hang quite frequently as well. Perhaps in -current or -stable things are > better? Horrid in what way? Slow writes? You can turn on NFS write clustering and async I/O, both violations of the NFS protocol specification (and the default for System V and Linux systems, where the write is ack'ed before it is performed, so if a crash happens before the write really happens, any files that clients are writing to may be corrupt when the server comes back up). Other errors? I am aware of problems in -current, but know of no problems in the release code... maybe you could be more specific? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.