9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Mon, 17 Dec 2007 14:24:01 -0500	[thread overview]
Message-ID: <fb2145080626b2a9df1687a5c38af616@csplan9.rit.edu> (raw)
In-Reply-To: <4042B3E6-0CA3-44FF-A78D-73ED333E393D@mac.com>

On Sun Dec 16 20:58:30 EST pietro10@mac.com wrote:
> I have no venti partition, and venti/conf asks for one called  
> v.arenas. The reason was that the default configuration of the  
> installer only gave fossil 700MB and venti/arenas 3GB. I wasn't sure  
> that would be sufficient for my files :-)
> 

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


  reply	other threads:[~2007-12-17 19:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16  2:48 Pietro Gagliardi
2007-12-16  9:10 ` Skip Tavakkolian
2007-12-16 14:22   ` Pietro Gagliardi
2007-12-16 16:25     ` erik quanstrom
2007-12-16 16:54       ` Pietro Gagliardi
2007-12-16 17:25         ` erik quanstrom
2007-12-16 23:57           ` Pietro Gagliardi
2007-12-17  1:34           ` Pietro Gagliardi
2007-12-17  1:36             ` Pietro Gagliardi
2007-12-17  1:42               ` erik quanstrom
2007-12-17  1:57                 ` Pietro Gagliardi
2007-12-17 19:24                   ` john [this message]
2007-12-17 21:10                     ` Pietro Gagliardi
2007-12-18 18:13                       ` erik quanstrom
2007-12-18 18:19                         ` erik quanstrom
2007-12-19 21:02                 ` Pietro Gagliardi
2007-12-20  1:15                   ` Juan M. Mendez
2007-12-20  1:52                     ` Pietro Gagliardi
2007-12-20  2:02                       ` erik quanstrom
2007-12-20  2:10                         ` Pietro Gagliardi
2007-12-20 19:58                           ` Pietro Gagliardi
2007-12-22 22:29                             ` Pietro Gagliardi
2007-12-23  2:35                               ` Bakul Shah
2007-12-27 16:23                               ` Russ Cox
2007-12-29 16:33                                 ` Pietro Gagliardi
2007-12-29 19:06                                   ` Pietro Gagliardi
2008-01-01  1:37                                 ` Pietro Gagliardi
2008-01-11 20:01                                   ` Pietro Gagliardi
2008-01-11 20:47                                     ` Pietro Gagliardi
2008-01-11 22:29                                       ` Pietro Gagliardi

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=fb2145080626b2a9df1687a5c38af616@csplan9.rit.edu \
    --to=john@csplan9.rit.edu \
    --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).