On Sat, 07 Jun 2014 21:39:29 BST Riddler <riddler...@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!
