From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Survey: Current Fossil+venti Filesystem
Date: Thu, 23 Jun 2011 11:03:18 +0100 [thread overview]
Message-ID: <3430e5ccdaef3475150d5d831dff1592@hamnavoe.com> (raw)
In-Reply-To: <20110623104644.5cd888d7@wks-ddc.exosec.local>
David du Colombier <0intro@gmail.com>:
> 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.
My experience is nearly the opposite of this. I've never lost any
active fossil data. And I agree that once data is archived to venti,
it is safe. But the daily archiving to venti can fail - sometimes
with "archWalk:" error messages and no dump made, but more often
silently leaving a dump with corrupted metadata in one or two
directories preventing access to anything below them in the tree.
More details in http://9fans.net/archive/2009/04/135 - I still haven't
tracked down the cause but I suspect a data race somewhere. It's an
irritation rather than a disaster because I've always been able to
patch up the bad metadata by hand. I quite enjoy a bit of disk
surgery now and then to keep my hand in.
next prev parent reply other threads:[~2011-06-23 10:03 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
2011-06-23 10:03 ` Richard Miller [this message]
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=3430e5ccdaef3475150d5d831dff1592@hamnavoe.com \
--to=9fans@hamnavoe.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).