All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Lenherr <thomas@lenherr.name>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs corrupts files
Date: Thu, 14 Oct 2004 21:58:22 +0200	[thread overview]
Message-ID: <416EDA5E.4020000@lenherr.name> (raw)
In-Reply-To: <1097774783.18925.10.camel@lade.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]

sorry, for forgetting the kernel of the workstation, it's yet another 
gentoo-kernel: 2.6.7-gentoo-r6.
i looked up the difference between the vanilla kernel 2.6.7 and this 
patched gentoo-version
and it seems it's not really much, just stuff like bootsplash, console 
speakup and something
about making it ready for supermount...

anyway, as you said i installed the original 2.6.8.1 on the server and 
tried the whole
thing again, what means i copied the 9 files over nfs and let them check 
with md5sum.
same result :(

i did not yet update the kernel of the workstation, because i accessed 
the nfs server
with an windows-implementation of nfs and experienced the same troubles. 
so i think
the server is the faulty one...

cheers,
thomas



Trond Myklebust wrote:

>På to , 14/10/2004 klokka 18:14, skreiv Thomas Lenherr:
>
>  
>
>>ok, here is what i did:
>>i had some files on an nfs-server (v3) using kernel 2.6.8-gentoo-r8
>>(updated because of the trouble). the 9 files had an average size of
>>about 180mB and i built the md5sums of these files via ssh _on_ this
>>server.
>>
>>after that i transferred these files to my workstation, once via nfs and
>>once via smb and let them check with md5sum again. the files transferred
>>with smb were ok, but 6 of the 9 files tranferred via nfs were corrupt.
>>then i made cmp between the local files (transferred with nfs of course)
>>and the files on the nfs-server. the result:
>>1) multiple use of cmp on files which md5sum mentioned as corrupt
>>resulted in reporting differences at different positions
>>2) sometimes the usage of cmp on files which md5sum mentioned as correct
>>resulted in reporting differences...
>>    
>>
>
>You don't mention which kernel the client was running. Was it the same
>as the server?
>
>Have you tried just grabbing a kernel 2.6.8.1 from ftp.kernel.org, and
>compiling it up (using the same .config as the gentoo kernel if you
>like) and then doing the same thing? I ask 'cos I just don't know what
>is in the gentoo kernels.
>
>Cheers,
>  Trond
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>NFS maillist  -  NFS@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nfs
>  
>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-10-14 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 16:14 nfs corrupts files Thomas Lenherr
2004-10-14 17:26 ` Trond Myklebust
2004-10-14 19:58   ` Thomas Lenherr [this message]
2004-10-18 15:30     ` Thomas Lenherr

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=416EDA5E.4020000@lenherr.name \
    --to=thomas@lenherr.name \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.