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>
In-Reply-To: <CAK3fRr_=e_JzBGPH-kWW6P8tQ-ZLhOpnFkd9kgGEmDxbHzJOhA@mail.gmail.com>
From:   Olga Kornievskaia <aglo@umich.edu>
Date:   Wed, 25 Mar 2020 12:09:33 -0400
Message-ID: <CAN-5tyH1TNrVoxPv0hcZ5gEpeHg6MOEjYhii+GCFM7urt_q1xQ@mail.gmail.com>
Subject: Re: Stuck NFSv4 mounts of Isilon filer with repeated
 NFS4ERR_STALE_CLIENTID errors
To:     James Pearson <jcpearson@gmail.com>
Cc:     Kevin Vasko <kvasko@gmail.com>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

Hi James,

What's in your /var/log/messages on the client that's looping?

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=3D1592911
but if the only thing that you see is RENEWs then it might not be it.


On Wed, Mar 25, 2020 at 10:02 AM James Pearson <jcpearson@gmail.com> wrote:
>
> On Wed, 25 Mar 2020 at 13:20, Kevin Vasko <kvasko@gmail.com> wrote:
> > James,
> >
> > Just curious are your symptoms anything similar to mine where if you tr=
ansfer a file (200MB+) to the NFS server, the transfer will just lock up an=
d never complete? Are you using Kerberos as well? If so...
> >
> > I had a problem on a Dell Unity box where on a transfer to the NFS serv=
er the sequence number gets out of order and it would lock up the Dell Unit=
y box NFS and the transfer would never complete.
> >
> > Dell was not aware of this bug and they had to have engineering look at=
 the issue. After about 3 months they got back with and had me change two p=
arameters.
> >
> > scv_nas ALL -parma -facility nfs -modify rpcgss.discardReplay -value 0
> >
> > scv_nas ALL -parma -facility nfs -modify rpcgss.discardOld -value 0
> >
> > I=E2=80=99m doubtful that this would be the same way you would change t=
hese settings on the Isilon but just figured if it=E2=80=99s related it mig=
ht help.
> > a Isilon
>
> We're not using Kerberos, just SYS_AUTH ...
>
> James