9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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:33:59 +0100	[thread overview]
Message-ID: <CAHqDL_8y_hNHAzCndr5Q7yqC_KAZfH4vzgH6am=5X4W=Srd++Q@mail.gmail.com> (raw)
In-Reply-To: <93bf184cc769cfc3e70f470d6876a1a8@quintile.net>

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

Hmm. On both my plan9port and on a 9front system I find printarenas.c, but
no script. Maybe you are thinking of the script for backup of individual
arenas to file? Yes, that could be a starting point.

Anyway, printarenas.c doesn't look too scary, basically a loop checking all
(or matching) arenas. It seems possible to modify the logic to start at a
specific offset.

Not running fossil at the moment, btw., my main file server is a Linux box,
but I use vac for backup, both at home and at work. Fossil is definitely on
my todo list, although the reported behavior when running out of space is a
bit scary. Do you know why it does not simply block further requests while
checkpointing to venti, or even better, starts a snapshot before it runs
out of space?

On Tue, Dec 12, 2017 at 3:07 PM, 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: 1893 bytes --]

  parent reply	other threads:[~2017-12-12 18:33 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
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 [this message]
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_8y_hNHAzCndr5Q7yqC_KAZfH4vzgH6am=5X4W=Srd++Q@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).