From: james palmer <email@example.com>
Subject: Re: [9front] Venti in 9front
Date: Tue, 07 Sep 2021 18:59:10 +0100 [thread overview]
Message-ID: <9DC0ABA8-F946-4E13-9DA8-385FB35DB2D1@biobuf.link> (raw)
> That's also a solution. I assume you used vac Did you change the 9fs
> script to fit the venti situation (9fs dump)?
yes i did use vac.
i changed 9fs to do "vacfs -m /n/dump /sys/lib/vac/dump.vac".
> It would be great if you could share more details (and scripts?) for your
> venti backup solution with cwfs nodump.
the script wasn't too complicated, pretty sure it was just:
vac -h fs -t -a /sys/lib/vac/dump.vac *
the cwfs with no dump is the same config as on the wiki. one thing to note is it uses the same code as the cache so it can't handle being full and you can't see how full it is.
prev parent reply other threads:[~2021-09-07 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 11:41 sirjofri
2021-09-05 4:51 ` unobe
2021-09-05 10:43 ` Stuart Morrow
2021-09-06 4:23 ` unobe
2021-09-06 7:45 ` sirjofri
2021-09-06 23:43 ` james palmer
2021-09-07 8:04 ` sirjofri
2021-09-07 17:59 ` james palmer [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).