Linux NFS development
 help / color / mirror / Atom feed
From: David Warren <warren@atmos.washington.edu>
To: nfs@lists.sourceforge.net
Subject: NFS caching problem
Date: Mon, 26 Sep 2005 12:13:39 -0700	[thread overview]
Message-ID: <43384863.10807@atmos.washington.edu> (raw)

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???
Thanks.

-- 
David Warren 		INTERNET: warren@atmos.washington.edu
(206) 543-0945		Fax: (206) 543-0308
University of Washington
Dept of Atmospheric Sciences, Box 351640
Seattle, WA 98195-1640




-------------------------------------------------------
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:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 19:13 David Warren [this message]
2005-09-26 19:36 ` NFS caching problem Peter Staubach
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=43384863.10807@atmos.washington.edu \
    --to=warren@atmos.washington.edu \
    --cc=nfs@lists.sourceforge.net \
    /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