From: Peter Staubach <staubach@redhat.com>
Subject: Re: statd for NFSv4 does not create file
Date: Thu, 14 Jul 2005 09:36:52 -0400
Message-ID: <42D66A74.8090205@redhat.com>
References: <20050714133019.30046.qmail@web51613.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	nfs@lists.sourceforge.net, steved@redhat.com
To: mehta kiran <kiranmehta1981@yahoo.com>
In-Reply-To: <20050714133019.30046.qmail@web51613.mail.yahoo.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

mehta kiran wrote:

>Hi Trond , 
>     Lock recovery worked with nfsv3 even if
>     nfs server fail over to some other system
>     This was possible because sm directory was shared
>     across systems.
>     Will this work with nfsv4 though there are
>     no files in sm directory. 
>

Yes, this should work.  NFSv4 will discover that the server has 
"rebooted" using
its mechanism and recover its locks.  The NFSv2 and NVFSv3 clients will 
discover
that the server has "rebooted" using the statd support and recover locks 
as well.

NFSv4 uses a different mechanism than NFSv2 and NFSv3, but if the failover
support was architected correctly, then things should continue to work.  You
may need to look at failover times perhaps.

       ps


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs