From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] mounting fossil
Date: Thu, 14 Mar 2013 10:23:47 -0400 [thread overview]
Message-ID: <2c69d0258a5cb3477c339d68766396a7@9srv.net> (raw)
In-Reply-To: <CAM6ozu7CBhf-t_BRWYPVa7Fm2yAcDkgLfir0Z99jc=R4yCgqxw@mail.gmail.com>
// I have an IDE HD with fossil (no venti) partition on it.
// It contains some data precious to me.
David's already provided good instructions on dealing with your
immediate problem, but allow me to take a step back:
Don't do that!
Fossil, without venti, is not the stablest thing around. I would very
strongly recommend against putting precious data on it. I've had it
go wonky personally, and there've been plenty of similar reports
here. In my experience, it's particularly vulnerable to unclean
shutdown, but I've seen more difficult-to-explain issues, too.
With venti, it's great: the snapshotting capabilties are very nice,
venti's very solid, and if your fossil does get out of whack, it's trivial
to re-initialize it from a known-good state from venti.
Anthony
next prev parent reply other threads:[~2013-03-14 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 8:35 Peter A. Cejchan
2013-03-14 9:41 ` David du Colombier
2013-03-14 14:23 ` a [this message]
2013-03-14 15:33 ` Peter A. Cejchan
2013-03-14 15:54 ` a
2013-03-15 7:43 ` Peter A. Cejchan
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=2c69d0258a5cb3477c339d68766396a7@9srv.net \
--to=a@9srv.net \
--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).