On Thu, 2018-06-21 at 09:34 -0700, Manjunath Patil wrote:
> The server may return NFS4ERR_NOSPC during NFSv4.1+ mount if there is
> a
> memory pressure to allocate a DRC slot for session being created. In
> such cases, try with lower nfs versions, which may succeed as DRC is
> shared by clients.
>
> Signed-off-by: Manjunath Patil <manjunath.b.patil@xxxxxxxxxx>
> ---
> utils/mount/stropts.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> index d1b0708..7e97a88 100644
> --- a/utils/mount/stropts.c
> +++ b/utils/mount/stropts.c
> @@ -881,6 +881,10 @@ check_result:
> case EINVAL:
> /* A less clear indication that our client
> * does not support NFSv4 minor version. */
> + case ENOSPC:
> + /* Server returned NFS4ERR_NOSPC for create session
> [NFSv4.1+].
> + * Try with lower NFS versions which share DRC
> amoung clients and
> + * hence low memory may be ok. */
> case EACCES:
> /* An unclear indication that the server
> * may not support NFSv4 minor version. */
This comment makes no sense. NFSv4.1 servers also share memory between
clients, and unlike older versions of NFS, they have ways to reclaim
that memory (see CB_RECALL_SLOT).
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
