From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil: disk is full
Date: Fri, 7 Mar 2003 09:33:51 +0100 [thread overview]
Message-ID: <ca209c638f81fcdd2dce78d5a4f2d956@plan9.escet.urjc.es> (raw)
In-Reply-To: <20030307101711.F13434@cackle.proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
I try just to keep the assumption that disk space is
unlimited. If you run fossil backed up by venti, a script
that clears all but the last N snapshots can keep your
fossil partition with enough space that it's not worth
reserving anything, IMHO.
[-- Attachment #2: Type: message/rfc822, Size: 2174 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil: disk is full
Date: Fri, 7 Mar 2003 10:17:11 +0200
Message-ID: <20030307101711.F13434@cackle.proxima.alt.za>
On Fri, Mar 07, 2003 at 08:52:05AM +0100, Fco.J.Ballesteros wrote:
>
> You can do what rsc said time ago, delete some snapshots before
> using snap -a. You can use epoch to do so.
Reserving space is ugly, but comes closer to the principle of least
surprise. Is there a (fixed) amount of disk space worth reserving?
++L
next prev parent reply other threads:[~2003-03-07 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 3:48 Kenji Arisawa
2003-03-07 7:52 ` Fco.J.Ballesteros
2003-03-07 8:17 ` Lucio De Re
2003-03-07 8:33 ` Fco.J.Ballesteros [this message]
2003-03-07 8:33 ` Kenji Arisawa
2003-03-07 8:43 ` Kenji Arisawa
2003-03-07 8:59 ` Lucio De Re
2003-03-07 9:11 ` Fco.J.Ballesteros
2003-03-07 9:19 ` Lucio De Re
2003-03-07 22:16 ` Axel Belinfante
2003-03-07 23:02 ` Russ Cox
2003-03-07 9:08 ` Fco.J.Ballesteros
2003-03-12 11:43 rog
2003-03-12 12:02 ` Axel Belinfante
2003-03-12 17:33 ` Russ Cox
2003-03-12 20:47 ` Russ Cox
2003-03-12 20:49 ` Russ Cox
2003-03-19 20:09 ` Axel Belinfante
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=ca209c638f81fcdd2dce78d5a4f2d956@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).