From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 23 Jun 2011 10:46:44 +0200
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Message-ID: <20110623104644.5cd888d7@wks-ddc.exosec.local>
In-Reply-To: <4E01F311.3060305@0x6a.com>
References: <4E01F311.3060305@0x6a.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Survey: Current Fossil+venti Filesystem
Topicbox-Message-UUID: f3fe5736-ead6-11e9-9d60-3106f5b1d025

I ran dozens of file servers with only Fossil or both Fossil and Venti
since 2004, and I never lost any byte of data.

I experienced only few problems with Fossil. Most of them caused Fossil
to freeze or, more rarely, to crash.

In most cases, I simply rebooted the file server, and it worked fine
again.

What I can say is:

 - these problems tend to appear far much often when running on virtual
   machines like Qemu,
 - running Fossil without Venti prevent some problems, like freezes
   during snapshot to Venti.

I am currently running something like twenty file servers (including
standalone machines), from 8GB to 1.5TB of storage. Most file servers
are running Fossil with Venti, but some are only running Fossil.
I mirror Venti through network and regularly backup arenas to DVDs
(but I am recently moving to BD).

So far, I only succeeded to reproduce data-lost problems on Fossil when
running heavy stress testing.

I can understand Fossil have problems and they might cause data
corruption, but when data is archived to Venti, you can be sure it will
stay forever.

These problems with Fossil just have to be fixed. I am currently working
on a fossil derivative which use libventi and libthread instead of
liboventi and eventually fix these problems. I am already running it
on some test file servers, but it's too early to talk about experiences
with it.

--
David du Colombier