From owner-freebsd-net@FreeBSD.ORG Tue Apr 11 12:16:11 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03F8E16A404 for ; Tue, 11 Apr 2006 12:16:11 +0000 (UTC) (envelope-from b.candler@pobox.com) Received: from proof.pobox.com (proof.pobox.com [207.106.133.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B915743D4C for ; Tue, 11 Apr 2006 12:16:07 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id D50B4E0CF4; Tue, 11 Apr 2006 08:16:06 -0400 (EDT) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id A4B6937739; Tue, 11 Apr 2006 08:16:05 -0400 (EDT) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FTHmu-000KCw-5N; Tue, 11 Apr 2006 13:16:04 +0100 Date: Tue, 11 Apr 2006 13:16:04 +0100 From: Brian Candler To: dima <_pppp@mail.ru> Message-ID: <20060411121604.GA77666@uk.tiscali.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: is NFS production-ready ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2006 12:16:11 -0000 On Mon, Apr 10, 2006 at 11:26:40PM +0400, dima wrote: > 3. Is at least implementation of NFS client (either kernel-side or > user-space) stable enough for production use? Client OS replacement is > impossible (hardly suitable, really) in my project. I built a big mail/web cluster a few years ago using FreeBSD 4.x (4.6.2 I think), where all the front-ends used NFS to access data on a shared fileserver platform (NetApp). It worked without a hitch, and still does. Regards, Brian.