Date: Wed, 12 Apr 2006 13:29:10 +0100 From: Brian Candler <B.Candler@pobox.com> To: dima <_pppp@mail.ru> Cc: freebsd-net@freebsd.org Subject: Re: is NFS production-ready ? Message-ID: <20060412122910.GA81569@uk.tiscali.com> In-Reply-To: <E1FTJPK-000MoC-00._pppp-mail-ru@f16.mail.ru> References: <20060411121604.GA77666@uk.tiscali.com> <E1FTJPK-000MoC-00._pppp-mail-ru@f16.mail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060412122910.GA81569>