From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica (was: ipv6)
Date: Tue, 28 May 2002 16:58:07 -0400 [thread overview]
Message-ID: <168410d616d1f548fd8bcb4b7d3db202@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 153 bytes --]
The file is consistent but is the directory? I.e. if I was copying over a whole bunch of files,
could he not have gotten in when I was half way through?
[-- Attachment #2: Type: message/rfc822, Size: 1967 bytes --]
From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica (was: ipv6)
Date: Tue, 28 May 2002 12:55:16 -0400
Message-ID: <38e0f7c1cf60157c1e74879ac4909e6c@plan9.bell-labs.com>
> Could there be a problem if pull has already opened the file
> and is copying it at the time an update is written to it.
> pull would have got the metadata of the file pre update.
> I'm assuming your local updates are faster than remote pulls
> so local update writes can 'overtake' the reads of a remote pull.
> Unlikely I know, but possible?
Nope. Pull stats the file before and after copying.
If a local write happened in the middle, the qid
returned by the second stat will be different, so
pull will copy it again. This repeats until the qid
stops changing.
Russ
next reply other threads:[~2002-05-28 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 20:58 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 22:19 rsc
2002-05-28 23:33 ` Micah Stetson
2002-05-28 21:28 rsc
2002-05-28 21:55 ` Chris Hollis-Locke
2002-05-28 16:55 rsc
2002-05-28 16:42 forsyth
2002-05-28 15:35 Russ Cox
2002-05-28 16:41 ` postmaster
2002-05-28 15:32 Russ Cox
2002-05-28 15:05 presotto
2002-05-28 12:29 [9fans] ipv6 presotto
2002-05-28 13:26 ` [9fans] replica (was: ipv6) Axel Belinfante
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=168410d616d1f548fd8bcb4b7d3db202@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).