public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Christian Robottom Reis <kiko@async.com.br>, NFS@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] NFS insanity
Date: Thu, 21 Jun 2001 09:59:18 -0400	[thread overview]
Message-ID: <424880000.993131958@tiny> (raw)
In-Reply-To: <Pine.LNX.4.32.0106202015380.2976-100000@blackjesus.async.com.br>



On Wednesday, June 20, 2001 08:23:06 PM -0300 Christian Robottom Reis
<kiko@async.com.br> wrote:

> 
> I've got an NFS server, version 2.4.4, using reiserfs with trond's NFS
> patches and the reiser-2.4.4 nfs patch.
> 
> On a client running 2.4.5 with trond's patches and the corresponding
> reiser patches, I get the wierdest behaviour:
> 
> # on client
> cp libgkcontent.so libgkcontent.so.x
> diff libgkcontent.so libgkcontent.so.x
> # no diff
> 
> # on server
> diff libgkcontent.so libgkcontent.so.x
> Binary files libgkcontent.so and libgkcontent.so.x differ
> 
> It _only_ happens in this file of all files I've tried out so far. I'm
> trying to get xdelta to show me what's differing so I can see if there's a
> pattern or something, but it's awful - data corruption not only possibly
> but happening. :-)
> 
> I haven't tried remounting yet to see what I get, but I don't see the
> problems on unpatched 2.4.2. I'll wait a bit to see if anyone has seen
> this. Anyone?

Sounds like some of the problems fixed in 2.4.5 and 2.4.6pre kernels, where
NFS data didn't get flushed right away, but I thought that only involved
mmap'd files.

-chris




  reply	other threads:[~2001-06-21 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 23:23 NFS insanity Christian Robottom Reis
2001-06-21 13:59 ` Chris Mason [this message]
2001-06-21 14:58   ` [reiserfs-list] " Trond Myklebust
2001-06-21 15:10 ` [NFS] " Trond Myklebust
2001-06-21 22:43   ` Christian Robottom Reis
2001-06-22 12:58     ` Trond Myklebust
2001-06-22 15:57       ` Christian Robottom Reis

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=424880000.993131958@tiny \
    --to=mason@suse.com \
    --cc=NFS@lists.sourceforge.net \
    --cc=kiko@async.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    /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