From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] running plan9 : an ideal setup?
Date: Wed, 19 Nov 2014 12:36:54 +0200 [thread overview]
Message-ID: <213a65f6538e0442f8b9744953dcbcbe@proxima.alt.za> (raw)
In-Reply-To: <bd2218a604d324753944f44abfec5490@quintile.net>
> I have been running fossil with snapshots for a year or so now and
> not had a single crash.
Is there an easy way to determine when a Fossil/Venti service was
first deployed? I have a feeling my specific installation is a good
few years old and I'm pretty sure any problem that may have arisen
could not have been hard to fix.
Just as a guideline:
ripple# hget 'http://127.1:8000/storage'
index=main
total arenas=25 active=14
total space=13,224,894,464 used=7,374,207,851
clumps=2,660,366 compressed clumps=2,197,678 data=15,481,985,505 compressed data=7,206,604,793
I don't keep media stuff, so a lot of this reflects changes over time
rather than quantity of data. I do have many versions of Go
development in place.
Lucio.
PS: It would seem I rebuilt the system (hoping to add disk capacity)
little over a year ago:
d-r-xr-xr-x S 0 proxima proxima 0 Jul 22 2013 /dev/sd00
This is a VMware ESX server permanently on.
next prev parent reply other threads:[~2014-11-19 10:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 13:29 Mayuresh Kathe
2014-11-18 13:53 ` dante
2014-11-18 14:11 ` Richard Miller
2014-11-18 14:28 ` dante
2014-11-27 20:57 ` Dante
2014-11-28 6:10 ` erik quanstrom
2014-11-28 6:54 ` David du Colombier
2014-11-28 8:42 ` Dante
2014-11-28 9:12 ` Mats Olsson
2014-11-28 9:18 ` Dante
2014-11-28 9:17 ` Richard Miller
2014-11-28 9:26 ` Dante
2014-11-28 13:20 ` erik quanstrom
2014-11-28 13:45 ` David du Colombier
2014-11-18 15:42 ` Kurt H Maier
2014-11-18 16:14 ` dante
2014-11-18 17:02 ` Aram Hăvărneanu
2014-11-18 20:29 ` Richard Miller
2014-11-18 21:28 ` Mats Olsson
2014-11-18 22:09 ` dante
2014-11-19 8:56 ` Mats Olsson
2014-11-26 17:16 ` Mats Olsson
2014-11-26 17:41 ` Dante
2014-11-26 17:56 ` Mats Olsson
2014-11-26 18:16 ` Mats Olsson
2014-11-26 18:41 ` Dante
2014-11-18 22:11 ` Skip Tavakkolian
2014-11-18 22:23 ` Steve Simon
2014-11-19 1:57 ` erik quanstrom
2014-11-19 5:36 ` Skip Tavakkolian
2014-11-19 5:59 ` lucio
2014-11-19 14:36 ` erik quanstrom
2014-11-19 15:34 ` Aram Hăvărneanu
2014-11-20 6:02 ` Anthony Sorace
2014-11-20 14:37 ` erik quanstrom
2014-11-20 18:43 ` Anthony Sorace
2014-11-21 14:34 ` erik quanstrom
2014-11-21 14:44 ` Anthony Sorace
2014-11-21 17:31 ` Bakul Shah
2014-11-22 18:06 ` erik quanstrom
2014-11-25 6:59 ` Bakul Shah
2014-11-25 11:10 ` erik quanstrom
2014-11-25 11:14 ` erik quanstrom
2014-11-25 13:52 ` Anthony Sorace
2014-11-25 14:26 ` erik quanstrom
2014-11-19 14:33 ` erik quanstrom
2014-11-19 20:05 ` Bakul Shah
2014-11-19 20:40 ` Tom Ivar Helbekkmo
2014-11-21 6:34 ` Harri Haataja
2014-11-19 2:04 ` erik quanstrom
2014-11-19 3:50 ` lucio
2014-11-19 9:40 ` Steve Simon
2014-11-19 9:50 ` dante
2014-11-19 10:18 ` Steve Simon
2014-11-19 10:27 ` dante
2014-11-19 18:55 ` Quintile
2014-11-19 10:36 ` lucio [this message]
2014-11-20 6:05 ` Anthony Sorace
2014-11-20 6:13 ` lucio
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=213a65f6538e0442f8b9744953dcbcbe@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).