From: Robert Raschke <r.raschke@tombobWEGDAMIT.com>
To: jorge-plan9@magma.com.ni, 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+plan9: disk full revisited
Date: Wed, 22 Nov 2006 11:23:11 +0000 [thread overview]
Message-ID: <e2a18f939e673f0a2f801ec386452347@tombob.com> (raw)
In-Reply-To: <871wnw49bk.fsf@jorgito.magma.com.ni>
Jorge-León wrote:
> It seems that this year I am the one who stumbled over the infamous
> "cacheAllocBlock: xxx1 disk is full" situation. No problem: I
> formatted and started over :-0
>
>
> The setup is a 100GB plan9 partition with about 14GB fossil and the
> rest venti, set up for confidence and performance tests of
> Plan9/fossil+venti in order to evaluate it for production use as a
> fileserver in the internal network at my work, with some Linux and a
> lot of Windows users.
>
[...snip...]
>
> While timed snapshots are really a nice thing for archiving, this
> feature maybe would make fossil+venti practically maintenance free.
You have to make sure that your fossil snapshots are recycled.
When you set up aotumatic snapshotting to venti using the fossil
snaptime command, make sure to set all three times: the archive to
venti, create fossil snapshot, and how long to keep fossil snapshots
around. My fossil is set up with
snaptime -a 0200 -s 60 -t 7200
Archive to venti at 2AM, keep hourly fossil snapshots and throw away
fossil snapshts oder than 7200 minutes (5 days).
Without the last entry, your fossil will _definitely_ run out of space.
That has happened to me twice in the past couple of years. I always
manage to get out of it by booting from a CD, mounting my fossil by
hand and running the 'epoch' command to ditch accumulated junk. I've so
far never had to rebuild my fossil/venti from scratch. That's going
back about two and half years now.
Robby
next prev parent reply other threads:[~2006-11-22 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 0:24 Georg Lehner
2006-11-22 11:23 ` Robert Raschke [this message]
2006-11-23 2:05 ` Dave Eckhardt
2006-11-29 21:10 ` Georg Lehner
2006-11-29 22:34 ` geoff
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=e2a18f939e673f0a2f801ec386452347@tombob.com \
--to=r.raschke@tombobwegdamit.com \
--cc=9fans@cse.psu.edu \
--cc=jorge-plan9@magma.com.ni \
/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).