From: Shehjar Tikoo <shehjart-+FkPdpiNhgJBDgjK7y7TUQ@public.gmane.org>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Short-reads on NFS client
Date: Thu, 30 Jul 2009 22:12:31 +0530 [thread overview]
Message-ID: <4A71CD77.2000505@gluster.com> (raw)
Hi All
Is there ever a possibility that a read syscall over linux nfs client
will return a short read? I think a short read is what I am observing
on our system with unfs3 as the NFS server. I've instrumented the
server and it seems to be returning the correct amount of data.
Is there any way I can debug this further?
I am running the 2.6.18-92.el5 kernel. The tool I am using is fileop
that is part of the iozone package. The original problem with the test
is that it outputs "Data mis-compare" error messages which means that
while doing a byte-to-byte comparison of what it wrote against the
data it read back from the file, it fails to see same contents as
written by it. On further hacking a bit with the code, I see that it
tries to compare X bytes in its buffer with Y bytes read from the
file, assuming that X will always be equal to Y. Is this assumption
supposed to hold for linux NFS client reads?
Thanks
Shehjar
reply other threads:[~2009-07-30 16:39 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=4A71CD77.2000505@gluster.com \
--to=shehjart-+fkpdpinhgjbdgjk7y7tuq@public.gmane.org \
--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 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.