From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica (was: ipv6)
Date: Tue, 28 May 2002 11:35:33 -0400 [thread overview]
Message-ID: <ad2ded07f58529b1dcfebe94b3f74ad9@plan9.bell-labs.com> (raw)
That whole message was about whether the replica
metadata and the file system remain consistent.
If you haven't updated for a long time and update
after new files have been written but before the log
is updated, you might get a new file that requires
other new or missing files to build correctly.
In that sense, you could end up with an inconsistent
set of files. But pulling again once the log has
been updated will fix that.
Russ
next reply other threads:[~2002-05-28 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 15:35 Russ Cox [this message]
2002-05-28 16:41 ` postmaster
-- 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 20:58 presotto
2002-05-28 16:55 rsc
2002-05-28 16:42 forsyth
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=ad2ded07f58529b1dcfebe94b3f74ad9@plan9.bell-labs.com \
--to=rsc@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).