From owner-freebsd-current@FreeBSD.ORG  Thu Apr 28 00:34:42 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1060)
	id 939231065674; Thu, 28 Apr 2011 00:34:42 +0000 (UTC)
Date: Wed, 27 Apr 2011 17:34:42 -0700
From: Craig Rodrigues <rodrigc@crodrigues.org>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20110428003442.GA31665@crodrigues.org>
References: <883894078.493543.1303672333362.JavaMail.root@erie.cs.uoguelph.ca>
	<201104260926.05033.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201104260926.05033.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.1i
Cc: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de>,
	freebsd-current@freebsd.org, Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: Heads Up: default NFS server changing to the new one
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2011 00:34:42 -0000

On Tue, Apr 26, 2011 at 09:26:05AM -0400, John Baldwin wrote:
> Actually, I think we should switch GENERIC in HEAD to the new client and 
> kernel very soon.  The goal is to get current users testing the new client and 
> server so they can uncover any bugs.  If problems crop up during the testing 
> that can't be resolved, we can always revert to the older client/server for 
> the release.

Hi,

I agree.  I think it is fantastic that Rick is doing all this work
in our NFS code.  Unfortunately, for this kind of stuff, in order
to uncover the interop issues and edge cases, it is better to make this
the default sooner, rather than later.  The people with the production
setups where you uncover these kinds of issues don't run
the tip of CURRENT usually....

One thing to consider:  if we could provide a bootable virtual machine with
the new NFS code to some of the storage vendors like EMC/Isilon, Netapp,
etc. it might be nice to get some feedback.  People are always busy,
but if we make the effort to make things easier to try out and test,
that is always a good thing.
 
-- 
Craig Rodrigues
rodrigc@crodrigues.org