mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siim Vahtre <siim@pld.ttu.ee>
To: linux-kernel@vger.kernel.org
Subject: nfs issues
Date: Sun, 6 Apr 2003 09:51:11 +0300 (EET DST)	[thread overview]
Message-ID: <Pine.GSO.4.53.0304060937020.17774@pitsa.pld.ttu.ee> (raw)


Hello.

I noticed something similar discussed before but I found no answer..

I downloaded a 700M ISO to a file server and then, as usually, tried
to md5sum it. When I md5summed it where I downloaded it, it was OK.
However, when I did md5sum over NFS, I got _different answers every
time I tried_. Also, I recieved much of these errors on the client
machine during the md5summing period:
"NFS: server cheating in read reply: count 8192 > recvd 1000"
(Server side did not give any errors.)

I have seen this error for many times before but I didn't count it
as anything serious. But when md5sum fails like that, then it means
NFS actually screws the data aswell, right?

The server is 2.4.20
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_TCP is not set
# CONFIG_NCPFS_NFS_NS is not set

And client is 2.5.66-bk10
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set

I think that these errors started to come along after I went over to 2.5.

             reply	other threads:[~2003-04-06  6:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  6:51 Siim Vahtre [this message]
2003-04-06 12:54 ` Trond Myklebust
2003-04-06 14:33   ` Siim Vahtre
2003-04-06 15:02     ` Trond Myklebust
2003-04-06 15:04       ` Siim Vahtre

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=Pine.GSO.4.53.0304060937020.17774@pitsa.pld.ttu.ee \
    --to=siim@pld.ttu.ee \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®