From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 topology
Date: Thu, 13 Jan 2011 20:22:46 -0800 [thread overview]
Message-ID: <AANLkTikzjXDH-jnM9TXnuZk5VPuSG95epHgNKePpRU7=@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101132110080.4272@fryrpg-zna>
On Thu, Jan 13, 2011 at 8:15 PM, Duke Normandin <dukeofperl@ml1.net> wrote:
> On Thu, 13 Jan 2011, John Floren wrote:
>
>> On 1/13/2011 7:42 PM, Duke Normandin wrote:
>>
>> > What is Venti again?
>>
>> Venti is the archival storage for Plan 9. Basically, new files and
>> changes to files get written to the Fossil file system. If Venti exists,
>> those changes get written to Venti; Venti never deletes anything and
>> works on a rather cool block-coalescing system. I highly recommend
>> reading the paper.
>
> I'll look for it. Sounds something like a RAID system to me. Or
> `vinum' on FreebSD.
>
>> On a system with a small disk, it's a good idea to go without Venti,
>> because of the space required. Fossil will then hold all your files,
>> meaning you don't get the daily snapshots, but you probably won't miss
>> those immediately--there's plenty of time to set up a system with a
>> bigger disk for Venti if you like Plan 9, or you could even add Venti
>> after the fact by sticking in another disk.
>
> What is the minimum HDD capacity required to run an Auth/cpu/fs server
> with Venti support?
There's no hard and fast rule, really, but your Fossil partition needs
to be at least big enough to hold the full distribution, and Venti
should be big enough to hold everything you ever intend to put on the
system.
I wouldn't try it with less than a 20 GB disk, with say 2 GB for
Fossil and the rest for Venti; unless you start storing music and
video on there, that should give you plenty of room to work with.
John
next prev parent reply other threads:[~2011-01-14 4:22 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 18:38 Duke Normandin
2011-01-13 18:48 ` dukeofperl
2011-01-13 18:50 ` David Leimbach
2011-01-13 19:16 ` Skip Tavakkolian
2011-01-13 19:31 ` Duke Normandin
2011-01-13 19:37 ` Jacob Todd
2011-01-13 19:44 ` Skip Tavakkolian
2011-01-13 20:08 ` Duke Normandin
2011-01-13 21:01 ` Tassilo Philipp
2011-01-13 21:39 ` Brian L. Stuart
2011-01-13 22:49 ` Duke Normandin
2011-01-14 3:27 ` blstuart
2011-01-14 4:02 ` erik quanstrom
2011-01-14 4:18 ` Duke Normandin
2011-01-14 4:04 ` Duke Normandin
2011-01-14 0:00 ` Federico G. Benavento
2011-01-14 3:26 ` Duke Normandin
2011-01-13 19:46 ` Bakul Shah
2011-01-13 20:11 ` erik quanstrom
2011-01-13 19:40 ` Duke Normandin
2011-01-13 20:07 ` John Floren
2011-01-13 20:24 ` Duke Normandin
2011-01-13 20:40 ` John Floren
2011-01-13 21:37 ` Duke Normandin
2011-01-13 21:59 ` Brian L. Stuart
2011-01-13 22:32 ` Duke Normandin
2011-01-13 23:18 ` John Floren
2011-01-14 3:42 ` Duke Normandin
2011-01-14 4:03 ` John Floren
2011-01-14 4:05 ` erik quanstrom
2011-01-14 4:15 ` Duke Normandin
2011-01-14 4:22 ` John Floren [this message]
2011-01-14 4:31 ` Duke Normandin
2011-01-14 4:35 ` Jacob Todd
2011-01-14 17:51 ` Bakul Shah
2011-01-14 17:54 ` erik quanstrom
2011-01-14 18:14 ` Bakul Shah
2011-01-14 19:13 ` erik quanstrom
2011-01-14 19:24 ` Duke Normandin
2011-01-14 20:44 ` Bakul Shah
2011-01-14 18:15 ` Charles Forsyth
2011-01-14 18:14 ` Federico G. Benavento
2011-01-14 18:35 ` Duke Normandin
2011-01-14 14:58 erik quanstrom
2011-01-14 17:14 ` Duke Normandin
2011-01-14 17:40 ` erik quanstrom
2011-01-14 18:58 ` Duke Normandin
2011-01-14 19:09 ` erik quanstrom
2011-01-14 19:23 ` Charles Forsyth
2011-01-14 19:22 ` Duke Normandin
2011-01-15 0:16 ` Charles Forsyth
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='AANLkTikzjXDH-jnM9TXnuZk5VPuSG95epHgNKePpRU7=@mail.gmail.com' \
--to=slawmaster@gmail.com \
--cc=9fans@9fans.net \
/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).