From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] growing/shrinking venti arena files -OR- arena file format
Date: Mon, 26 Nov 2012 09:07:19 +0200 [thread overview]
Message-ID: <d274d0677036491d9d5f52e1422d1a31@proxima.alt.za> (raw)
In-Reply-To: <86haochpd8.fsf@cmarib.ramside>
> Is
> there a TECHNICAL SPECIFICATION for the arena file format?
The source code is eminently readable and the "words" directory (in
/sys/src/cmd/venti) contains quite a bit of details, at a glance. I'd
say there's enough there to make an educated guess or two.
In my experience, the most sensible way to resize disk capacity for
venti is to back up the arenas and then rewrite them to the new
format. I didn't expect it when I did it by accident, but it seems
practical, if not particularly fast. That, of course, may be a good
reason not to mess with arena sizes, it is hard to restore them
without spending a lot of time on them.
++L
next prev parent reply other threads:[~2012-11-26 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 6:04 smiley
2012-11-26 7:07 ` lucio [this message]
2012-11-26 13:42 ` erik quanstrom
2012-11-26 16:12 Brian L. Stuart
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=d274d0677036491d9d5f52e1422d1a31@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).