Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail-wi0-f178.google.com ([209.85.212.178]:50681 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754886Ab2ITQGt (ORCPT ); Thu, 20 Sep 2012 12:06:49 -0400 Received: by wibhr14 with SMTP id hr14so907686wib.1 for ; Thu, 20 Sep 2012 09:06:48 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 20 Sep 2012 12:06:48 -0400 Message-ID: Subject: Re: unhandled error -10026 From: Andy Adamson To: William Dauchy Cc: Linux NFS mailing list , R.Eggermont@tudelft.nl Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Sep 20, 2012 at 10:34 AM, William Dauchy wrote: > On Tue, Sep 18, 2012 at 11:49 AM, William Dauchy wrote: >> I'm getting a trace following an unhandled error on a linux nfs client >> 3.4.7 x86_64. >> NFS: nfs4_reclaim_open_state: unhandled error -10026. Zeroing state > > For the moment I don't know if the error is coming from a bad server > implementation or if it's on client side. Should I assume that this an > error that should never hit the client? Yes. The client only sends OPEN reclaims after noting the server has rebooted due to previously receiving an NFS4ERR_STALE_CLIENTID or NFS4ERR_STALE_STATEID error from a state-full operation (RENEW, OPEN, OPEN_DOWNGRADE, OPEN_CONFIRM, CLOSE, LOCK, LOCKU) which triggers the client to establish a new clientid via SETCLIENTID/SETCLIENTID_CONFIRM. Upon server reboot, all state that the previous server instance had is invalid - including OPEN seqid's. So, the server returning NFS4ERR_BAD_SEQID (10026) on an OPEN reclaim is illegal. -->Andy > > Regards, > -- > William > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html