From: Rue Mohr <sn0297@sunshine.net>
To: linux-nfs@vger.kernel.org
Subject: nfs kernel server bug
Date: Sun, 07 Feb 2021 09:18:01 -0800 [thread overview]
Message-ID: <602020C9.50705@sunshine.net> (raw)
I'm having an issue where the kernel server is dishing out all zeros for file content being read over NFS. The file byte
count is correct.
Writing files is fine.
With the same client, a different server works just fine.
I have been trying to pin this down, so far all I know is that the packets from the server actually contain zeros for
the file contents.
The troubled server kernel is 5.4.1
Has anyone encountered this or is it just me?
next reply other threads:[~2021-02-07 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 17:18 Rue Mohr [this message]
2021-02-08 11:58 ` nfs kernel server bug Benjamin Coddington
2021-02-23 22:59 ` J. Bruce Fields
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=602020C9.50705@sunshine.net \
--to=sn0297@sunshine.net \
--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