9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Fossil+Venti on Linux
Date: Sun, 25 May 2008 10:59:20 -0400	[thread overview]
Message-ID: <f1cf3a41167ff85430528b2444a53f7b@9srv.net> (raw)
In-Reply-To: <20080525075632.GA30260@nibiru.local>

I'm not running Linux, but I've run venti+fossil on Mac OS X for testing. I
intend to use venti there regularly once I figure out how to get OS X to let
me get at a raw partition that isn't mounted (anyone?).

I don't think venti+fossil will do what you're looking for, however, at least
not without some additional machinery. Fossil doesn't do any replication or
fail-over: it must talk to zero or one ventis. Venti doesn't automatically
replicate anything, either, although that's pretty easy to script if you're
willing to accept the exposure of a cron job. It's true you could run multiple
fossils off one venti, but they'll be logically distinct (just getting the block
aggregation benifits of sharing a venti backing store).

I believe the Plan B folks did some work with fail-over (amongst other
things) that might be applicable. Beyond that, if you want to get what you
want from venti+fossil, you'll need to inject a filter in front of one of those
two to do the fail-over (and handle all the fun of tracking writes and
propagating them when the server comes back, and so on).

If you're looking to back up *existing* Linux boxes, then fossil might not
be what you want anyway. Take a look at vbackup(8) and friends (I'm
trying to convince it I'm on an HFS+ partition). You'll have to figure out
the correct procedures for your site, but the examples are pretty useful.
Still no automatic fail-over, but a cron job could probably get you
replication.
Anthony




  reply	other threads:[~2008-05-25 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25  7:56 Enrico Weigelt
2008-05-25 14:59 ` a [this message]
2008-05-25 15:48   ` Francisco J Ballesteros
2008-05-25 20:24     ` erik quanstrom
2008-05-26 12:58   ` Enrico Weigelt
2008-05-26 14:01     ` erik quanstrom
     [not found]     ` <78feb60ec33f8a38ccbc38625b6ea653@quanstro.net>
2008-05-29  9:12       ` Enrico Weigelt
2008-05-29  9:27         ` Christian Kellermann
2008-05-29 12:17           ` Enrico Weigelt
2008-05-29 13:51             ` Russ Cox
2008-05-29 12:26         ` erik quanstrom
2008-05-29 13:33           ` Wes Kussmaul

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=f1cf3a41167ff85430528b2444a53f7b@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    --cc=weigelt@metux.de \
    /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).