From: Trond Myklebust <trondmy@kernel.org>
To: "zhangjian (CG)" <zhangjian496@huawei.com>,
anna@kernel.org, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Question]nfs: never returned delegation
Date: Thu, 05 Mar 2026 23:49:41 -0500 [thread overview]
Message-ID: <80c9ba69f1d35928ea9d21e146e60f194cff7405.camel@kernel.org> (raw)
In-Reply-To: <23b52d16-4b74-43e4-9fff-73ac57c9ef89@huawei.com>
On Fri, 2026-03-06 at 10:46 +0800, zhangjian (CG) wrote:
> Hi experts on NFS:
>
> Recently we meet an error:
> 1.Nfs wait for sunrpc
> 2.Sunrpc send OPEN message and hang the rpc task onto sunrpc pending
> queue.
> 3.Server never reply, and since NFS_CS_NO_RETRANS_TIMEOUT is forced
> and
> connection is ESTABLISHED, task will never be retransmitted.
> This cause procedures waiting on this file hang forever.
> I know using "umount -f " to kill rpc task works. And the key to the
> problem most likely lies in the network layer. But should nfs
> retransmit
> it after waiting for so long?
>
> Wish for reply. Thanks
>
> Zhangjian
>
Please read the NFSv4 spec. It very clearly states that the client
should never retransmit unless the connection breaks.
IOW: the problem here is your broken server, not the client.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2026-03-06 4:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:48 [Question]nfs: never returned delegation zhangjian (CG)
2025-08-11 13:03 ` Trond Myklebust
2025-08-12 2:51 ` zhangjian (CG)
2025-09-01 9:07 ` Li Lingfeng
2025-09-01 11:40 ` Jeff Layton
2025-09-01 14:12 ` Li Lingfeng
2025-08-11 13:03 ` Jeff Layton
2025-08-11 13:06 ` Trond Myklebust
2025-08-12 2:45 ` zhangjian (CG)
2026-03-06 2:46 ` zhangjian (CG)
2026-03-06 4:49 ` Trond Myklebust [this message]
2026-03-12 4:19 ` [Question]nfs: should nfs timeout even with NFS_CS_NO_RETRANS_TIMEOUT ? zhangjian (CG)
2026-03-12 13:09 ` Trond Myklebust
2026-03-13 3:22 ` zhangjian (CG)
2026-03-13 15:18 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80c9ba69f1d35928ea9d21e146e60f194cff7405.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=zhangjian496@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.