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>
In-Reply-To: <8B8B914C-D741-42E0-BC0C-4850635B5551@gmail.com>
From:   James Pearson <jcpearson@gmail.com>
Date:   Wed, 25 Mar 2020 14:00:42 +0000
Message-ID: <CAK3fRr_=e_JzBGPH-kWW6P8tQ-ZLhOpnFkd9kgGEmDxbHzJOhA@mail.gmail.com>
Subject: Re: Stuck NFSv4 mounts of Isilon filer with repeated
 NFS4ERR_STALE_CLIENTID errors
To:     Kevin Vasko <kvasko@gmail.com>
Cc:     "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

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 tran=
sfer a file (200MB+) to the NFS server, the transfer will just lock up and =
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 server=
 the sequence number gets out of order and it would lock up the Dell Unity =
box NFS and the transfer would never complete.
>
> Dell was not aware of this bug and they had to have engineering look at t=
he issue. After about 3 months they got back with and had me change two par=
ameters.
>
> 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 the=
se settings on the Isilon but just figured if it=E2=80=99s related it might=
 help.
> a Isilon

We're not using Kerberos, just SYS_AUTH ...

James