linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Cc: SteveD@redhat.com, Charles.Lever@netapp.com
Subject: Re: NFS problems with Linux-2.4
Date: Tue, 27 May 2003 13:29:38 -0400	[thread overview]
Message-ID: <20030527172938.GA26434@ncsu.edu> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C6113127532@lavender-fe.eng.netapp.com>

Hello All,
    I wanted to follow up this thread now that I have a working solution.

My initial problem was that machine A would create a file and machine B
would attempt to stat() or open() it over NFS and it would not be there.
I was using the 2.4.7 kernel that came with Red Hat 7.2.

Trond suggested I try a more recent kernel since 2.4.7 had known close
to open cache consistency problems.  I tried the 2.4.20 kernel and it
did make the problem better, but it was still there.

Someone suggested doing an opendir() to flush the NFS cache.  This did
make the problem go away with the 2.4.20 kernels.  With the 2.4.7
kenrels, I started getting ESTALE errors after I did this.  I found
that I could work around these errors by doing something like:

    f = fopen(filename, mode);

    if(!f) {
      if(errno==ESTALE) {
	sleep(1);
	f = fopen(filename,  mode);
      }
    }

which is ugly, but it allow me to run on unpatched Red Hat 7.2 systems
which is highly desirable.

Thanks,

Jim

       reply	other threads:[~2003-05-27 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482A3FA0050D21419C269D13989C6113127532@lavender-fe.eng.netapp.com>
2003-05-27 17:29 ` jlnance [this message]
2003-05-13 14:50 NFS problems with Linux-2.4 jlnance
2003-05-13 15:19 ` Trond Myklebust
2003-05-15 15:22   ` Jim Nance
2003-05-18 15:00     ` Trond Myklebust
2003-05-19  0:53       ` jlnance
2003-05-19 11:27         ` Trond Myklebust
2003-05-19 20:02       ` Jim Nance
2003-05-13 19:07 ` jjs
2003-05-13 19:24   ` Roland Dreier
2003-05-13 21:55     ` jjs
2003-05-13 23:11   ` Alan Cox

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=20030527172938.GA26434@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --cc=Charles.Lever@netapp.com \
    --cc=SteveD@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).