From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org
Subject: short read from NFS client
Date: Mon, 7 May 2012 12:52:25 -0500 [thread overview]
Message-ID: <20120507175225.GA15419@us.ibm.com> (raw)
Hi All,
An application running on an NFS file got short read (received
fewer bytes than requested). At the same time, we noticed few ESTALE
errors for NFS READ Calls in the tcpdump. We lost few packets in the
tcpdump, so can't say if there were any other errors at that time. What
are the circumstances (other than the ones listed below) where NFS
client can send a short read to the application in buffered read system
call?
EOF is not reached, no direct I/O is involved, and the read syscall is not
interrupted, of course!
Thanks, Malahal.
next reply other threads:[~2012-05-07 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 17:52 Malahal Naineni [this message]
2012-05-07 18:51 ` short read from NFS client Myklebust, Trond
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=20120507175225.GA15419@us.ibm.com \
--to=malahal@us.ibm.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;
as well as URLs for NNTP newsgroup(s).