From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: NFS file consistency
Date: Mon, 17 Mar 2003 09:50:54 -0500 [thread overview]
Message-ID: <20030317145054.GA7030@ncsu.edu> (raw)
Hello All,
I am trying to track down some file consistency problems I am seeing
and I want to make sure my assumptions about NFS are correct.
Say I have 2 NFS clients, machine A and machine B. Machine A does
an open/write/close on a file. After this machine B does an open/read on
the file. Is machine B guaranteed to read the same data that A wrote
or is there a delay between the time A closes the file and the time B
can expect to see valid data? Also if the file already existed before
A wrote it, and B had already read from it and closed it, does this
affect anything?
Thanks,
Jim
next reply other threads:[~2003-03-17 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 14:50 jlnance [this message]
2003-03-17 15:00 ` NFS file consistency Trond Myklebust
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=20030317145054.GA7030@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--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 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.