9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Update on Fossil+Venti Stuff
Date: Wed, 21 Mar 2007 22:02:36 +0100	[thread overview]
Message-ID: <20070321210235.GA10654@shodan.homeunix.net> (raw)
In-Reply-To: <9ab217670703211317o1958d9b3u647f6ac4fac758cd@mail.gmail.com>

Fossil is more like a write _buffer_ for venti. The interaction with venti
takes place during the nightly dumps (at 5am for a default install; can be
configured according to your needs). Fossil also regularly takes snapshots
that aren't archived to venti. (Again, for a default setup snapshots every
hour, kept for 8 days; can be configured otherwise.) The snapshots are taken
for files that changed since the last snaptime; dumps are taken from files
where the current epoch is greater than the last written to venti. Those
procedures are quite well documented.

The problems seem to arise when you write lots of new data between dumps
(more than the fossil size; can be less when taking into account
intermediate snapshots). I've been thinking about ways to cope with that
lately, but wasn't too eager to post here until I'd actually have time 
to really delve into it (next month, or so). At the moment those are little
more than some elaborations of possibilities already mentioned in the
archives. I could do a write-up of what I could think of so far later
tonight when I'm back home if there is wider interest in exploring possible
enhancements (I'm not thinking of those asfixes) to fossil. I think it
could be worthwhile, though.

	Martin

P.S. I'm sure one could describe the current workings in more detail, but
I'm too much in a hurry now.



  reply	other threads:[~2007-03-21 21:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 20:17 Devon H. O'Dell
2007-03-21 21:02 ` Martin Neubauer [this message]
2007-03-21 21:05 ` erik quanstrom
2007-03-21 21:24 ` Bakul Shah
2007-03-22 10:04 ` Richard Miller
2007-03-23  5:17   ` Devon H. O'Dell
2007-03-23  6:14     ` Martin Neubauer
2007-03-23  6:27       ` Devon H. O'Dell
2007-03-23  6:54         ` Martin Neubauer
2007-03-23 14:24           ` David Leimbach
2007-03-23 15:04             ` Devon H. O'Dell
2007-03-23 15:10               ` Richard Miller
2007-03-23 15:29                 ` Devon H. O'Dell
2007-03-23 15:39                   ` Richard Miller
2007-03-23 15:47                     ` Devon H. O'Dell
2007-03-23 19:23                     ` Steve Simon
2007-03-23 15:47                   ` Richard Miller

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=20070321210235.GA10654@shodan.homeunix.net \
    --to=m.ne@gmx.net \
    --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).