From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7468fd6eb15a3b3e45fc69efcddb4a54@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Sat, 21 Oct 2006 10:57:12 +0100
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keeping an eye on disk use
In-Reply-To: <7d3530220610201905uef42ffet8b27e314f13e1caf@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: cfb14e1a-ead1-11e9-9d60-3106f5b1d025

> ... It *seems*, based on things I've read, that Fossil
> simply stores new files until they can be written to Venti, at which
> point the file is simply replaced by a pointer to the appropriate data
> in Venti.

Yep, this is right, usually snapshots to venti take place every night
so you can only write (or change) a bit less than 6Gb of data per day but
you can store 20Gb in total. The 20Gb are compressed and all duplicate
blocks are merged so that 20Gb goes a long way. If you are dumping large
amounts of data into venti - copying old backup CDs into venti to make them
online, then you can do a snapshot to venti manually to flush out fossil
and free some space in it.

Fossil and venti have served me well and been very reliable - failing disks
are less good but there is a proceedure for recovery.

-Steve