Linux NFS development
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: David Warren <warren@atmos.washington.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS caching problem
Date: Mon, 26 Sep 2005 15:36:45 -0400	[thread overview]
Message-ID: <43384DCD.5040004@redhat.com> (raw)
In-Reply-To: <43384863.10807@atmos.washington.edu>

David Warren wrote:

> I have discovered a wierd problem with NFSv3 on linux.
> I have 3 machines
> machine A and B  both mount a disk D  from machine C
> The options are tcp,rw,hard and intr.
>
> Program test runs on machine A writing to D:
> (fortran)
>      program test
>      do i=1,10
>         call system("/bin/rm t")
>         open (10, file='t', status='new')
>         write(10,*)i
>         write(6,*)i
>         close(10)
>         call sleep(1)
>      enddo
>      end
>
> program t2 runs on machine B reading from D:
> (c, but doesn't have to be)
> #include <stdlib.h>
> #include <fcntl.h>
> main(){
>  char in[80];
>  int file;
>  int len;
>
>  while(1){
>    file=open("t", O_RDONLY);
>    len=read(file,in,79);
>    in[len]='\0';
>    printf("%s\n",in);
>    close(file);
>  }
> }
>
> while machine A is counting 1 - 10 and placing these numbers into file 
> t, machine B is continually reading 1 from file t, then after a while 
> it will switch to another number and read it for a while. In my first 
> version of this, I was opening and rewriting the same file. In that 
> version, machine B always read 1's. Now that I am creating new inodes 
> all the time, it changes every few minutes while I repeatedly rerun 
> test on machine A.
>
> Now for the other interresting facts:
> Reading this file from an unrelated sun during this produces the same 
> result as machine B.
> The same thing under NFSv4 does not do this. It works exactly as one 
> would expect it to. As soon as the file is writen, the reader sees the 
> new data.
>
> Any ideas what I could have done wrong in my NFSv3 set up? Is there 
> some kernel parameter that need tweaking? is there some mount option I 
> should have??? 


What version(s) of Linux are on machines, A, B, C?  What is the local file
system on machine, C, which is on disk, D?

    Thanx...

       ps


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-09-26 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 19:13 NFS caching problem David Warren
2005-09-26 19:36 ` Peter Staubach [this message]
2005-09-26 20:01 ` Trond Myklebust
2005-09-26 20:11   ` Peter Staubach
  -- strict thread matches above, loose matches on Subject: below --
2006-11-13 15:47 nfs " Bernd Schubert
2007-04-20 17:35 NFS " David Warren

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=43384DCD.5040004@redhat.com \
    --to=staubach@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=warren@atmos.washington.edu \
    /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