On Wed, Oct 1, 2014 at 9:49 AM, Anna Schumaker <Anna.Schumaker@xxxxxxxxxx> wrote: > On 09/27/2014 11:54 PM, Trond Myklebust wrote: >> If a NFSv4.x server returns NFS4ERR_STALE_CLIENTID in response to a >> CREATE_SESSION or SETCLIENTID_CONFIRM in order to tell us that it rebooted >> a second time, then the client will currently take this to mean that it must >> declare all locks to be stale, and hence ineligible for reboot recovery. >> >> RFC3530 and RFC5661 both suggest that the client should instead rely on the >> server to respond to inelegible open share, lock and delegation reclaim >> requests with NFS4ERR_NO_GRACE in this situation. > Has our handling of NFS4ERR_NO_GRACE been tested in this situation? nfs4_reclaim_open_state() will handle it by calling nfs4_state_mark_reclaim_nograce(), which clears the flags enabling reboot recovery, and sets the NFS_STATE_RECLAIM_NOGRACE flag to force state reclaim using standard OPEN and LOCK. -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
