From: Nikolai Zhubr <zhubr.2@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Continuation of failed RPC request after unmount
Date: Sun, 06 Jun 2021 00:02:38 +0300 [thread overview]
Message-ID: <60BBE66E.6080806@gmail.com> (raw)
Hi all,
I'm debugging some likely buggy network device driver. Let's say the
driver erroneously looses some packets (under certain conditions). One
of important tests is being able to mount and use NFS share (as a
client). I'm currently using kernel 4.14.221 and NFS v3 in UDP mode.
While testing, I've noticed some strange NFS behaviour. If some NFS
request (file read) obtains no response (let's suppose due to
connectivity issue), such request will be resent periodically (in hope
to eventually succeed). This is expected. Now I observe, that after I
unmount the NFS share (successfully), the failed requests still keep
being resent, apparently infinitely (Confirmed by e.g. Wireshark),
surviving also ifdown and ifup. So basically, I've found no way to get
rid of them other than reboot.
Is this a known behaviour? Is it by design? Does it make any sense?
Thank you,
Regards,
Nikolai
reply other threads:[~2021-06-05 20:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=60BBE66E.6080806@gmail.com \
--to=zhubr.2@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox