9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] plan9port fossil
Date: Thu, 19 Mar 2020 14:34:16 +0200	[thread overview]
Message-ID: <CAJQ9t7jK3weC0hvENF+3srgLJhBNitJpAbdrM4pHF=nHBG6esA@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKGNfQbNaZwPyM+GxGX3jhuTJP8AGvFbd8Ms6mdW2qb6ew@mail.gmail.com>

On 3/18/20, Steven Stallion <sstallion@gmail.com> wrote:
[ ...]
>
> I've had a lot of luck using venti from plan9port with fossil running
> natively on my plan9 fileserver. I keep a directory on sources (now
> 9p.io) with some notes and example scripts on how to make this work:
> http://9p.io/sources/contrib/stallion/venti/. The biggest benefit to
> this configuration is it makes offsite backups a breeze from the Linux
> host.
>
Nice stuff, Steven. I found my small Linuxmint workstation not up to
the task, the worst symptom being that shutting venti down takes a
very long time, tens of minutes, I think. It didn't matter when the
host was on all the time, but of late power blackouts have made that
untenable.

What I wish to contribute here is that using an external drive and
configuring it as a raw image allows it to be used (I presume even
shared) between Venti hosts. My most recent (and pretty old)
configuration is this:

$ cat sdb.conf
index	main

isect	/dev/sdb3:0k-20774910k
arenas	/dev/sdb3:20774911k-418906111k
bloom	/dev/sdb3:418906112k-419430400k

mem	80m
bcmem	160m
icmem	256m

addr	tcp!*!venti
httpaddr	tcp!*!8008

Sadly, there is at least one damaged block and I did not have the
foresight to set the drive up as a mirror or better.  It is not
critical, but that would be helpful.

The equally low priority problem I mentioned in the past: vacfs on p9p
truncates all large files on reading. Cinap suggested checking for
mixed-size pointer/integer types, but that becomes a mission. Still,
it is worth doing.

The native version of vacfs works flawlessly and mounts quite
successfully under p9p.

Lucio.

  reply	other threads:[~2020-03-19 12:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  3:30 kim.lassila
2020-03-18 15:37 ` [9fans] " Steven Stallion
2020-03-19 12:34   ` Lucio De Re [this message]
2020-03-25  1:32     ` Plan9 on virtual machine in Mac os Mark Everett
2020-03-25  6:39       ` [9fans] " Cyber Fonic
2020-03-25 18:00         ` Ethan Gardener
2020-03-25 20:11           ` Brian L. Stuart
2020-03-25 22:17             ` Ethan Gardener
2020-03-25  6:44       ` Cyber Fonic
2020-03-25 21:35         ` Mark Everett
2020-03-25 21:43           ` Skip Tavakkolian
2020-03-25 10:04       ` Kim Lassila
2020-03-25 21:24       ` Skip Tavakkolian
2020-03-25 21:30       ` Nicolas S. Montanaro
2020-03-25 22:21         ` Ethan Gardener
2020-04-02 12:09     ` [9fans] plan9port fossil Ole-Hjalmar Kristensen
2020-04-02 13:37       ` Lucio De Re
2020-03-20  3:41   ` Kim Lassila
2020-04-01 23:52 ` cigar562hfsp952fans
2020-04-02  0:59   ` [9fans] " Jeremy Jackins
2020-04-02  1:23     ` Jeremy Jackins
2020-04-04 13:45       ` [9fans] " Kim Lassila

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='CAJQ9t7jK3weC0hvENF+3srgLJhBNitJpAbdrM4pHF=nHBG6esA@mail.gmail.com' \
    --to=lucio.dere@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).