From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A potentially useful venti client
Date: Tue, 12 Dec 2017 10:23:16 -0600 [thread overview]
Message-ID: <CAGGHmKFyx2wtSs6yu3Cq8ZFhQCAjpSnaWS9BFsTr=Wcwbzwz9w@mail.gmail.com> (raw)
In-Reply-To: <e03f9dae4789398a9705f2fea4d9b45c@quintile.net>
It depends - the 30GB I was mentioning before was from an older Ken's
fs that I imported with a modified cwfs. Rather than deal with all of
the history, I just took a snap with vac -s of the latest state of the
file system. I keep the original dump along with the cwfs binary in
case I ever need to dig into the dump (I haven't needed to in years).
The last venti store I needed to move around I was able to just use
rdarena/wrarena to reconstitute the fs on new hardware.
I think it comes down to what you want to preserve - life gets easier
if you don't need to worry about the dump. I don't think it would be
too tough to script the dump though. You probably would just need to
walk through each successive vac and archive it using vac -a. Probably
easier said than done though :-)
Steve
On Tue, Dec 12, 2017 at 10:11 AM, Steve Simon <steve@quintile.net> wrote:
> Interesting.
>
> how did you do the import? did you use vac -q and vac -d previous-score for each
> imported day to try and speed things up?
>
> Previously I imported stuff into venti by copying it into fossil first
> and then taking a snap. I always wanted a better solution, like being able
> to use vac and then installing the score into my main filesystem through
> a special fscons command. Sadly I never got around to it.
>
> -Steve
>
next prev parent reply other threads:[~2017-12-12 16:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 9:33 Ole-Hjalmar Kristensen
2017-12-12 14:07 ` Steve Simon
2017-12-12 15:45 ` Steven Stallion
2017-12-12 16:11 ` Steve Simon
2017-12-12 16:23 ` Steven Stallion [this message]
2017-12-12 18:42 ` Ole-Hjalmar Kristensen
2017-12-12 19:16 ` Steven Stallion
2017-12-12 20:31 ` hiro
2017-12-12 23:36 ` Skip Tavakkolian
2017-12-13 10:17 ` Bakul Shah
2017-12-12 18:33 ` Ole-Hjalmar Kristensen
2017-12-12 19:53 ` Steve Simon
2017-12-12 20:03 ` Steve Simon
2017-12-12 20:07 ` Ole-Hjalmar Kristensen
2017-12-12 20:15 ` Steve Simon
2017-12-12 20:31 ` Ole-Hjalmar Kristensen
2017-12-12 20:38 ` Steve Simon
2017-12-12 21:40 ` Ole-Hjalmar Kristensen
2017-12-13 0:03 ` Steve Simon
2017-12-13 7:29 ` Ole-Hjalmar Kristensen
2017-12-13 9:44 ` hiro
2017-12-13 11:00 ` Steve Simon
2017-12-13 12:22 ` Richard Miller
2017-12-13 14:13 ` Ole-Hjalmar Kristensen
2017-12-13 13:37 ` Ole-Hjalmar Kristensen
2017-12-12 21:02 ` Steven Stallion
2017-12-12 21:55 ` Ole-Hjalmar Kristensen
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='CAGGHmKFyx2wtSs6yu3Cq8ZFhQCAjpSnaWS9BFsTr=Wcwbzwz9w@mail.gmail.com' \
--to=sstallion@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).