9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fossil+Venti system memory requirements to be aware of?
Date: Thu, 20 Oct 2016 13:41:04 -0500	[thread overview]
Message-ID: <CAGGHmKE=9LEvYTifupSir0Mtdv20bjt=dKfPcLeo9+wZ=PHmMw@mail.gmail.com> (raw)
In-Reply-To: <868ttidh05.fsf@cmarib.ramside>

On Thu, Oct 20, 2016 at 1:15 PM,  <cigar562hfsp952fans@icebubble.org> wrote:
> Steven Stallion <sstallion@gmail.com> writes:
>
>> Sizing venti is also simple.
>
> I disagree with this.  The best way to configure venti depends largely
> on how you plan to use it.  I have multiple venti servers configured for
> different uses.  For example, I keep my DVD images on a different venti
> server than I do for smaller, more frequently-used files such as mail.

see venti(8); there's plenty of advice on configuring your store with
rough estimations for an initial conf file. Once you decide your
geometry, it's trivial to extend the number of arenas in the store,
just remember to reindex.

> I don't know that to be true.  If the source and destination volumes are
> the same size, yes, it's easy to just dd the arenas.  But if you're
> relocating to a smaller/larger partition, what would be an easy way to
> do that?

see venti-backup(8).



  reply	other threads:[~2016-10-20 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19  8:41 James A. Robinson
2016-10-19 10:17 ` Aram Hăvărneanu
2016-10-19 17:16   ` James A. Robinson
2016-10-19 16:44 ` Steven Stallion
2016-10-20 18:15   ` cigar562hfsp952fans
2016-10-20 18:41     ` Steven Stallion [this message]
2016-10-20 21:42       ` Steve Simon
2016-10-20 21:54       ` Steve Simon
2016-11-02 18:44   ` James A. Robinson
2016-11-02 19:02     ` Steven Stallion
2016-10-20 17:50 ` cigar562hfsp952fans

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='CAGGHmKE=9LEvYTifupSir0Mtdv20bjt=dKfPcLeo9+wZ=PHmMw@mail.gmail.com' \
    --to=sstallion@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).