From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Survey: Current Fossil+venti Filesystem
Date: Thu, 23 Jun 2011 16:20:01 +0000 [thread overview]
Message-ID: <861uyky0y6.fsf@cmarib.ramside> (raw)
In-Reply-To: <4E01F311.3060305@0x6a.com> (Jack Norton's message of "Wed, 22 Jun 2011 08:50:09 -0500")
Jack Norton <jack@0x6a.com> writes:
> I'd like to know some recent real world experiences with
> fossil+venti. This stems from rumors that for some people, fossil has
> a history of data loss. I don't like rumors (or data loss), and I'm
Maybe newbies tend to bang on the edges of fossil more than the old
hats, but I've encountered a couple of problems with fossil+venti.
(1) A fresh fossil+venti install on a ThinkPad T23 resulted in a file
system with read errors. (Discussed in a previous thread on this list.)
On the other hand, a fossil-only install on the same machine worked
fine. This was resolved by using a 9atom kernel and enabling DMA in
plan9.ini.
(2) I once experienced something really bizarre, whereby doing something
like a cp/dircp over a file resulted in corruption of the backed up
copy. If I recall correctly, the snap/archive (don't remember which)
copy of the file thereafter contained zero bytes, even though both the
previous and new versions of the file were non-zero in length. This is
probably a problem with how fossil+venti handle file truncation. I
learned to tiptoe around that by using rm before cp/dircp.
Other than those, I've never lost data with fossil+venti... at least in
the whole three months or so this noob's been using them. :) YMMV.
--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
prev parent reply other threads:[~2011-06-23 16:20 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
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 [this message]
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=861uyky0y6.fsf@cmarib.ramside \
--to=smiley@zenzebra.mv.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).