9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question about fossil
Date: Sun,  8 Jun 2014 00:03:55 -0700	[thread overview]
Message-ID: <20140608070355.A8B9DB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 07 Jun 2014 21:39:29 BST." <CAGMcHPqOp2ovwZK93DWMKyUkZpPJTSZwA4dZNWsYMOxyz8MUeQ@mail.gmail.com>

On Sat, 07 Jun 2014 21:39:29 BST Riddler <riddler876@gmail.com> wrote:
>
> Onto my question: What if I shrunk that fossil partition to, say, 1GB
> and then wrote either more than 1GB in small files or a single 2GB
> file.

Why would you want to make the fossil partition that small?

I would keep it at least twice as large as the largest file
I'd ever want to create.

> Will fossil error on the write that pushes it over the edge?
> Perhaps 'spill' the extra data over to venti?
> Something else entirely?

I haven't studied fossil but AFAIK it won't spill data to
venti when it runs low on disk. Rather, you set it up to take
daily snapshots so the partition should be large enough to
hold all the new data you may generate in a day.

Other things to note:

- make sure you mirror or backup the venti disk or else you
  may lose the only copy of a block!
- try this out on a small scale before you commit to it, as I
  suspect you'll run into various limits and may be bugs. Do
  report what you discover.
- performance will likely be poor. For better performance you
  may want to keep venti index on a separate (flash) disk.
- it would be nice if you can come up with a workable setup
  for a venti server!



  parent reply	other threads:[~2014-06-08  7:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 20:39 Riddler
2014-06-07 23:17 ` Steve Simon
2014-06-07 23:49   ` Riddler
2014-06-08  8:04     ` erik quanstrom
2014-06-09 20:25       ` Riddler
2014-06-08  8:30     ` Steve Simon
2014-06-08  8:39       ` erik quanstrom
2014-06-08  7:03 ` Bakul Shah [this message]
2014-06-08  7:56   ` erik quanstrom
2014-06-08 16:56     ` Bakul Shah
2014-06-08 17:06       ` erik quanstrom
2014-06-10 10:59       ` Nicolas Bercher
2014-06-09 20:21   ` Riddler
2014-06-09 21:12     ` Lyndon Nerenberg
2014-06-09 21:25       ` erik quanstrom
2014-06-09 21:52         ` Bakul Shah
2014-06-09 22:22           ` erik quanstrom
2014-06-09 22:36             ` Bakul Shah
2014-06-10  0:15               ` Brian L. Stuart
2014-06-10  4:24                 ` Bakul Shah

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=20140608070355.A8B9DB827@mail.bitblocks.com \
    --to=bakul@bitblocks.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).