Date: Mon, 30 Mar 2009 13:38:48 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: Pete French <petefrench@ticketswitch.com> Cc: pjd@freebsd.org, freebsd-stable@freebsd.org, marck@rinet.ru Subject: Re: ZFS and NFS: changing handles between reboots Message-ID: <5f67a8c40903301038i31e18598ld17c645548b6feda@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40903301038i31e18598ld17c645548b6feda>