From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <73b576df1e95d643f8c6bc65c6598bd9@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Tue, 18 Dec 2007 13:13:25 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
In-Reply-To: <72A04C0E-4AF2-4EBC-B697-050A610B19BF@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 1c5ba1f6-ead3-11e9-9d60-3106f5b1d025

> Then where are the nodes stored?
> 
> On Dec 17, 2007, at 2:24 PM, john@csplan9.rit.edu wrote:
>
[...]
> >
> > Unless I completely misunderstand the way venti and fossil work, that
> > would be quite sufficient unless you plan on creating more than
> > about 700 MB of files in a day. After you install, fossil will  
> > flush everything
> > to venti, which *should* get you a pretty much empty fossil  
> > partition--
> > it's just a cache, remember. Your files will then be moved from fossil
> > to venti every night thereafter. Since venti practices block  
> > compression,
> > it shouldn't be much of a problem to have venti... unless you copy in
> > a whole bunch of mp3 files and then decide you don't want them *after*
> > venti has written them.
> > I used a fossil+venti system to store a bunch of music at one  
> > point. I would
> > fill up the fossil buffer with mp3s, then force a sync to venti,  
> > then re-fill
> > the fossil buffer, repeating until I had transferred everything and  
> > written
> > it to venti.
> > If the things I've said here are wrong or don't make sense, let me  
> > know.
> >
> > John