All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@kenjo.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: NFS corruption on 2.6.11.7
Date: Tue, 24 May 2005 00:47:07 +0200	[thread overview]
Message-ID: <1116888428.5206.14.camel@tiger> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 597 bytes --]

I have both the server and client running  2.6.11.7 and have some severe
data corruption when reading from the server (maybe on write also I have
not tested).

If I copy the data over with scp or ftp I get correct data. Also  nfs
works OK with a mac os x 10.4 client.

Running gen.sh on the server and then cmp.sh on the client results in a
md5 checksum difference on 5-12 files I have never done one run where
there was no errors. 

This is what cat /proc/mounts reports on the nfs mount

:/export/home/ken /home/ken nfs rw,v3,rsize=32768,wsize=32768,hard,udp,lock,addr=amd 0 0



[-- Attachment #1.2: gen.sh --]
[-- Type: application/x-shellscript, Size: 176 bytes --]

[-- Attachment #1.3: cmp.sh --]
[-- Type: application/x-shellscript, Size: 147 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-05-23 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 22:47 Kenneth Johansson [this message]
2005-05-24  0:35 ` NFS corruption on 2.6.11.7 Trond Myklebust
2005-05-24  1:04   ` Trond Myklebust
2005-05-24 10:15   ` Kenneth Johansson
2005-05-24 12:01     ` Trond Myklebust
2005-05-24 14:58       ` Kenneth Johansson
2005-05-25 20:13       ` Kenneth Johansson
     [not found]         ` <20050525.131616.59655785.davem@davemloft.net>
2005-05-25 20:34           ` Kenneth Johansson

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=1116888428.5206.14.camel@tiger \
    --to=ken@kenjo.org \
    --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 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.