From owner-freebsd-stable@FreeBSD.ORG  Mon Mar 30 18:08:10 2009
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 24951106564A
	for <freebsd-stable@freebsd.org>; Mon, 30 Mar 2009 18:08:10 +0000 (UTC)
	(envelope-from zbeeble@gmail.com)
Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com
	[209.85.217.176])
	by mx1.freebsd.org (Postfix) with ESMTP id 9ADAA8FC18
	for <freebsd-stable@freebsd.org>; Mon, 30 Mar 2009 18:08:09 +0000 (UTC)
	(envelope-from zbeeble@gmail.com)
Received: by gxk24 with SMTP id 24so6063687gxk.19
	for <freebsd-stable@freebsd.org>; Mon, 30 Mar 2009 11:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=wUSx1Gf2So2lEGFmApnCKAMftu6lrgRL1+qVuZjTwEU=;
	b=G75af+NTh89KLHsBw+UobzemOOwvKLQID8ZAMQxRDwARBGtKbw1xCh4+fvZOEeD5yN
	ZXw15x904TfPqeY9oAfpxhQ08puEZZoOMAg15vELtABE9ce+INCQRAvq2dg6wWLYJ9vZ
	ABgxMA1txJYZSnZmk5VrkVVjQQhKCN375Us0o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=OttAIZFpe4OP/67KDu2Vd5ByCO8CLCCNv54cAnT0FrIrootm4IeRRXDEFrnj0Yph64
	0KLVtUy5QHsc0gz62m/b7gOf/NeYaC5fMyZEhwrQqdxGSv6RGdZSxsBN3asGlrYHyfL2
	DhGKDmjLWU+0wM4f9M/1aaVxuJebQFRAAEVjg=
MIME-Version: 1.0
Received: by 10.150.149.19 with SMTP id w19mr10552431ybd.56.1238434728622; 
	Mon, 30 Mar 2009 10:38:48 -0700 (PDT)
In-Reply-To: <E1LoFor-000D9h-5k@dilbert.ticketswitch.com>
References: <alpine.BSF.2.00.0903300035550.30609@woozle.rinet.ru>
	<E1LoFor-000D9h-5k@dilbert.ticketswitch.com>
Date: Mon, 30 Mar 2009 13:38:48 -0400
Message-ID: <5f67a8c40903301038i31e18598ld17c645548b6feda@mail.gmail.com>
From: Zaphod Beeblebrox <zbeeble@gmail.com>
To: Pete French <petefrench@ticketswitch.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: pjd@freebsd.org, freebsd-stable@freebsd.org, marck@rinet.ru
Subject: Re: ZFS and NFS: changing handles between reboots
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2009 18:08:10 -0000

On Mon, Mar 30, 2009 at 7:38 AM, Pete French <petefrench@ticketswitch.com>wrote:

> > on any request to previously mounted FS. On UFS, mounted NFS file systems
> > survive server reboots...
>
> Are you sure anout that ? I have a lot of systems sharing files using UFS
> and I see the 'stale NFS file handle' thing if I reboot the server too.
> No ZFS involved there.


Hrnh?  I noticed that the NFS file handle was "stale" when I upgraded from
7.1 to 8.0 ... and I chalked that up to the upgrade changing the calculation
of the cookie that NFS uses for a ZFS share, but reboots of an NFS server
are meant to be transparent to the clients (save the downtime involved).

Typically, stale NFS file handle indicates that the mount the client
currently sees does not have the same hash as the mount it was using.

Seeing this on ZFS would be a bug.  Seeing this on UFS would just be
strange...