From owner-freebsd-net@FreeBSD.ORG Tue Apr 11 14:10:30 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 086B816A407 for ; Tue, 11 Apr 2006 14:10:30 +0000 (UTC) (envelope-from zanecb@midwest-connections.com) Received: from mail.midwest-connections.com (mail.midwest-connections.com [69.148.152.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8644C43D45 for ; Tue, 11 Apr 2006 14:10:29 +0000 (GMT) (envelope-from zanecb@midwest-connections.com) Received: (qmail 5132 invoked by uid 503); 11 Apr 2006 14:13:28 -0000 Received: from unknown (HELO zerda) (zanecb@69.155.32.130) by 0 with ESMTPA; 11 Apr 2006 14:13:28 -0000 Date: Tue, 11 Apr 2006 09:10:45 -0500 From: "Zane C.B." To: freebsd-net@freebsd.org Message-ID: <20060411091045.231f0e94@zerda> In-Reply-To: References: <20060411121604.GA77666@uk.tiscali.com> Organization: Midwest Connections Inc. X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dima <_pppp@mail.ru> 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 14:10:30 -0000 On Tue, 11 Apr 2006 17:59:50 +0400 dima <_pppp@mail.ru> wrote: > > 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. > > What is the reaction on network/NAS failure? > I mean, I'm about to provide transparent storage service in the case > of failures of different types. Not sure about currently, but it use to have a problem with if there was a failure, it would go into a wait state forever. I've not run into this in a very long time and this was suppose to have been fixed a month or two ago.