Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <9932cd04adc20b73040d82c605acb0b5a24e3855.camel@hammerspace.com>
 <8B8B914C-D741-42E0-BC0C-4850635B5551@gmail.com> <CAK3fRr_=e_JzBGPH-kWW6P8tQ-ZLhOpnFkd9kgGEmDxbHzJOhA@mail.gmail.com>
 <CAN-5tyH1TNrVoxPv0hcZ5gEpeHg6MOEjYhii+GCFM7urt_q1xQ@mail.gmail.com>
In-Reply-To: <CAN-5tyH1TNrVoxPv0hcZ5gEpeHg6MOEjYhii+GCFM7urt_q1xQ@mail.gmail.com>
From:   James Pearson <jcpearson@gmail.com>
Date:   Wed, 25 Mar 2020 17:10:31 +0000
Message-ID: <CAK3fRr-BeEYdQjA14Y8oqfjXw=kkVqf2pF0vvpVkqXDqGcAZ8g@mail.gmail.com>
Subject: Re: Stuck NFSv4 mounts of Isilon filer with repeated
 NFS4ERR_STALE_CLIENTID errors
To:     Olga Kornievskaia <aglo@umich.edu>
Cc:     "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Wed, 25 Mar 2020 at 16:09, Olga Kornievskaia <aglo@umich.edu> wrote:
>
> Hi James,
>
> What's in your /var/log/messages on the client that's looping?

Nothing but 'nfs:server isilon not responding, still trying'

> If your network traces had some interleaved SETCLIENTIDs I would have
> said that it's possible you are hitting this RHEL7.5 problem:  Bug
> 1592911 - Fix how client ID in SETCLIENTID is constructed to prevent
> lease tempering. https://bugzilla.redhat.com/show_bug.cgi?id=1592911
> but if the only thing that you see is RENEWs then it might not be it.

It is quite possible whatever the issue is has been fixed in a more
recent RHEL/CentOS 7 kernel - we haven't (yet?) seen the issue on
machines that have been upgraded to CentOS 7.7 ...

Thanks

James