9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] multiple venti servers
Date: Wed, 30 Aug 2006 16:27:19 -0400	[thread overview]
Message-ID: <ee9e417a0608301327h45147c38yef41950630dabdea@mail.gmail.com> (raw)
In-Reply-To: <dac0a5820608300901g4e1a0d12sb1ce0737747243f1@mail.gmail.com>

> If I am right, one problem with this approach is it becomes tricky
> when both venti servers have updates but yet to be sync'ed. And, in
> particular, when there are identical data backed up (say, I downloaded
> a CD image in two machines and backed up in these two servers), it
> leaves two copies. It may be safe but it does leave two copies.

You are not right.

Since venti coalesces writes, it doesn't matter if both servers sync
to each other.  You'll waste a little bandwidth resending some writes,
but you will not end up with multiple copies of a block on the same
venti server.

Russ


  parent reply	other threads:[~2006-08-30 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 20:46 John Floren
2006-08-30  4:37 ` Russ Cox
2006-08-30  5:13   ` geoff
2006-08-30 13:42     ` Wes Kussmaul
2006-08-30 15:02       ` Francisco J Ballesteros
2006-08-30 16:01         ` Tharaneedharan Vilwanathan
2006-08-30 16:02           ` William Josephson
2006-08-30 16:12             ` LiteStar numnums
2006-08-30 18:23             ` Francisco J Ballesteros
2006-08-30 21:51               ` Robert Raschke
2006-08-30 20:27           ` Russ Cox [this message]
2006-09-01  6:40             ` Tharaneedharan Vilwanathan
2006-09-01 17:55               ` Russ Cox
2006-09-03 12:53                 ` Tharaneedharan Vilwanathan

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=ee9e417a0608301327h45147c38yef41950630dabdea@mail.gmail.com \
    --to=rsc@swtch.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).