From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] How to read fossil+venti partition without venti
Date: Wed, 23 Apr 2008 09:52:32 +0100 [thread overview]
Message-ID: <a68fc1e322ca880a8d588de622641d8b@quintile.net> (raw)
In-Reply-To: <5049A218-A739-4CC0-89EE-D05AB851506A@mac.com>
Once you have run fossil with venti and it has done its first snap -a,
which is usually done after the first fossil+venti boot, you can now
never run fossil without venti. Fossil now contains only the files
which have changed since the last snap -a. All other files which have
not changed WRT the snap are reprisented by pointers (scores) into
the venti archive; This is fundamental to how fossil and venti work.
What you can do is run venti without fossil and extract your data from
there (using vacfs) provided you can get a score which reprisents the
root of the filesystem you are after (use fossil/last on your fossil
partition).
You can also completely repopulate your fossil as of the time of that
last snap -a losing only the changes between the snap -a and the time
your system crashed.
I wrote a "hold your hand" document, primarily for my own use, which
describes rebuilding a working system from only the venti arenas.
http://plan9.bell-labs.com/sources/contrib/steve/doc/Venti-rescue.pdf
I strongly suggest you print out the fossil and venti papers and manual
pages and read them carefully.
-Steve
prev parent reply other threads:[~2008-04-23 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 1:48 Pietro Gagliardi
2008-04-23 3:21 ` Bruce Ellis
2008-04-23 20:57 ` Pietro Gagliardi
2008-04-23 22:01 ` Steve Simon
2008-04-23 8:52 ` Steve Simon [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=a68fc1e322ca880a8d588de622641d8b@quintile.net \
--to=steve@quintile.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).