From: Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@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 19:42:51 +0100 [thread overview]
Message-ID: <CAHqDL_9NBcFbNbTGfQCmOk7_UkhscH9evyOpBE-KWa0aHT1Bhg@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKGafi=2gAjucoCz-UtU5i_+5L7=7HVQn=mcvqaPwt-bjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
Thanks for the tip about mounting with 9fs. I have used vacfs on Linux ,
though.
But why so slow? Did you import a root with lots of backup versions? It was
partly because of that I made this client which can import venti blocks
without needing to traverse a file tree over and over again.
On Tue, Dec 12, 2017 at 4:45 PM, Steven Stallion <sstallion@gmail.com>
wrote:
> Get ready to wait! It took almost a month for me to import about 30GB
> from a decommissioned file server. It was well worth the wait though -
> if you place the the resulting .vac file under /lib/vac (or
> $home/lib/vac) you can just use 9fs to mount with zero fuss.
>
> On a related note, once sources starting having issues with
> availability, I started running nightly snaps of my contrib directory
> via cron:
>
> contrib=/n/sources/contrib/$user
> 9fs sources
> @{cd $contrib && vac -a $home/lib/vac/contrib.vac .} >[2]/dev/null
>
> Now I have a dump-like history of changes I've made to my contrib
> directory without the need to connect to sources:
>
> % 9fs contrib.vac
> % lc /n/contrib
> 2015 2016 2017
>
> Cheers,
> Steve
>
> On Tue, Dec 12, 2017 at 8:07 AM, Steve Simon <steve@quintile.net> wrote:
> > printarenas is a script - it walks through all your arenas at each
> offset.
> >
> > You could craft another script that remembers the last arena and offset
> you successfully
> > transferred and only send those after that.
> >
> > I think there is a pattern where you can save the last arena,offset in
> the local
> > fossil. Then you could mount the remote venti to check that last
> arena,offset
> > that actually arrived and stuck to the disk on the remote site.
> >
> > On a similar subject I have 10 years of backups from a decomissioned
> work server
> > that I need to merge into my home venti one of these days...
> >
> > -Steve
> >
>
>
[-- Attachment #2: Type: text/html, Size: 2424 bytes --]
next prev parent reply other threads:[~2017-12-12 18:42 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
2017-12-12 18:42 ` Ole-Hjalmar Kristensen [this message]
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=CAHqDL_9NBcFbNbTGfQCmOk7_UkhscH9evyOpBE-KWa0aHT1Bhg@mail.gmail.com \
--to=ole.hjalmar.kristensen@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).