From: Adrian Tritschler <ajft@ajft.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] venti survey
Date: Mon, 23 Jun 2008 22:16:14 +1000 [thread overview]
Message-ID: <485F940E.4000909@ajft.org> (raw)
In-Reply-To: <20080619152245.2CFE31E8C53@holo.morphisms.net>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Russ Cox wrote:
> I am curious about the relative sizes of people's venti
> servers, how much data they have stored, and how
> quickly they are filling.
>
> Please run
>
> hget http://my-venti-url/storage >/tmp/v
> hget http://my-venti-url/index >>/tmp/v
>
> mail -s 'venti survey' rsc@swtch.com </tmp/v
>
> In a week or so I will post a summary.
Russ,
If it is of interest to you I've attached the logs of the ventis that
I've run for the last year or two. In both cases they've been running
on plan9ports, with arenas and indexes held in files in linux filesystems.
The logs are from venti running on two linux systems:
fafnir: venti used for "tinkering" and vbackup of some very small linux
file systems
nidhogg/w-cl28-g34-c: venti for a VMware guest plan9 cpu server, and
vbackup of some linux systems. (The hostname changed
I put the logging into my crontab ages ago with the intention of
generating my own graphs but never got around to it.
The logs were generated with a very simplistic hourly cron job containing:
VENTILOG=$HOME/log/venti-$HOSTNAME.log
$PLAN9/bin/date -n >> $VENTILOG
$PLAN9/bin/hget http://localhost:1088/storage >> $VENTILOG
> Thanks.
> Russ
Adrian
[-- Attachment #2: venti.zip --]
[-- Type: application/zip, Size: 199184 bytes --]
next prev parent reply other threads:[~2008-06-23 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 15:23 Russ Cox
2008-06-23 12:16 ` Adrian Tritschler [this message]
2008-06-24 2:39 ` [9fans] " Adrian Tritschler
2008-06-24 3:00 ` Uriel
2008-06-26 20:16 ` Eric Van Hensbergen
2008-06-26 20:18 ` erik quanstrom
2008-06-26 21:06 ` Juan Céspedes
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=485F940E.4000909@ajft.org \
--to=ajft@ajft.org \
--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).