Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Apr 2006 09:10:45 -0500
From:      "Zane C.B." <zanecb@midwest-connections.com>
To:        freebsd-net@freebsd.org
Cc:        dima <_pppp@mail.ru>
Subject:   Re: is NFS production-ready ?
Message-ID:  <20060411091045.231f0e94@zerda>
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, 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060411091045.231f0e94>