From: "Peter A. Cejchan" <tyapca7@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mounting fossil
Date: Thu, 14 Mar 2013 16:33:47 +0100 [thread overview]
Message-ID: <CAM6ozu5U6Jf1PLsoyZdu1Suz0UT-BUB0ZJbcFEGFjd6RWW4d-A@mail.gmail.com> (raw)
In-Reply-To: <2c69d0258a5cb3477c339d68766396a7@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
Thanks for warning!
However, I reorganize my data very often, moving between dirs, renaming,
reorganising tree structure...
How will Venti cope with this?
Fopr now, I plan to put the data onto an ext2 partition for now, until I
feel the dir tree is well-designed.
I just want to mount the fossil partition and copy the data out of there.
Thanks, best,
++pac
On Thu, Mar 14, 2013 at 3:23 PM, <a@9srv.net> wrote:
> // 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
>
>
>
[-- Attachment #2: Type: text/html, Size: 1605 bytes --]
next prev parent reply other threads:[~2013-03-14 15:33 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
2013-03-14 15:33 ` Peter A. Cejchan [this message]
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=CAM6ozu5U6Jf1PLsoyZdu1Suz0UT-BUB0ZJbcFEGFjd6RWW4d-A@mail.gmail.com \
--to=tyapca7@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).