9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Survey: Current Fossil+venti Filesystem
Date: Thu, 23 Jun 2011 10:46:44 +0200	[thread overview]
Message-ID: <20110623104644.5cd888d7@wks-ddc.exosec.local> (raw)
In-Reply-To: <4E01F311.3060305@0x6a.com>

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



  parent reply	other threads:[~2011-06-23  8:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 13:50 Jack Norton
2011-06-22 14:02 ` erik quanstrom
2011-06-22 15:13 ` Charles Forsyth
2011-07-03  9:07   ` Steve Simon
2011-06-23  8:46 ` David du Colombier [this message]
2011-06-23 10:03   ` Richard Miller
2011-06-23 10:35   ` Adrian Tritschler
2011-06-23 14:51   ` Jack Norton
2011-06-23 15:25     ` dexen deVries
2011-06-23 15:27       ` erik quanstrom
2011-06-23 15:57         ` ron minnich
2011-06-23 16:19           ` erik quanstrom
2011-06-23 16:28             ` ron minnich
2011-06-23 16:37               ` erik quanstrom
2011-06-23 18:47               ` Bakul Shah
2011-06-24 22:44                 ` Akshat Kumar
2011-06-23 16:56           ` Charles Forsyth
2011-06-23 16:58           ` Charles Forsyth
2011-06-23 17:02         ` Jack Norton
2011-06-23 17:50           ` erik quanstrom
2011-06-23 15:27     ` Charles Forsyth
2011-06-23 15:57     ` David du Colombier
2011-06-23 16:20 ` smiley

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=20110623104644.5cd888d7@wks-ddc.exosec.local \
    --to=0intro@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).