From owner-freebsd-net@FreeBSD.ORG  Wed Apr 12 12:29:14 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 B0F8516A401
	for <freebsd-net@freebsd.org>; Wed, 12 Apr 2006 12:29:14 +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 581A243D48
	for <freebsd-net@freebsd.org>; Wed, 12 Apr 2006 12:29:14 +0000 (GMT)
	(envelope-from b.candler@pobox.com)
Received: from proof (localhost [127.0.0.1])
	by proof.pobox.com (Postfix) with ESMTP id 90DEBE3118;
	Wed, 12 Apr 2006 08:29:13 -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 5AF6B3A578;
	Wed, 12 Apr 2006 08:29:12 -0400 (EDT)
Received: from lists by mappit.local.linnet.org with local (Exim 4.60
	(FreeBSD)) (envelope-from <b.candler@pobox.com>)
	id 1FTeT9-000LEH-0m; Wed, 12 Apr 2006 13:29:11 +0100
Date: Wed, 12 Apr 2006 13:29:10 +0100
From: Brian Candler <B.Candler@pobox.com>
To: dima <_pppp@mail.ru>
Message-ID: <20060412122910.GA81569@uk.tiscali.com>
References: <20060411121604.GA77666@uk.tiscali.com>
	<E1FTJPK-000MoC-00._pppp-mail-ru@f16.mail.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1FTJPK-000MoC-00._pppp-mail-ru@f16.mail.ru>
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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2006 12:29:14 -0000

On Tue, Apr 11, 2006 at 05:59:50PM +0400, dima wrote:
> > 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.

It never came up as an issue. The backend was a clustered NetApp pair, so if
one failed, the other head-end would take over the disks belonging to the
first one, and continue to serve from the same IP address.

However, I believe that if you do a "soft" mount, and the server goes away,
eventually the client will get an I/O error. The client program has to be
written in such a way as it will handle I/O errors in all situations (and
many are not)

Regards,

Brian.