From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <645393765206d0ff808837fb7cea1632@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] df for fossil?
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <93b0889692ef974561c174f7b857b343@plan9.escet.urjc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 14 Jan 2003 11:10:29 -0500
Topicbox-Message-UUID: 4113c350-eacb-11e9-9e20-41e7f4b1d025

There are two separate issues here.

#1:
You don't ever need a `rescue' kernel.  It's unlikely that a kernel
with any particular preordained set of tools would be that helpful
without being enormous.  A bootable CD with the full system
(which already exists) would be a lot more helpful.

#2:
Fossil does *not* reserve two blocks for emergency archival
snapshots.  As of today there are times when you would get stuck
and not be able to do anything.  However, that *only* happens when:

	- your disk is full
	- *and* you have no snapshots to discard or refuse to discard them
	- *and* you refuse to delete one of your active files to make space

Notice that being ``stuck'' requires stubbornness on your part
in addition to Fossil being out of disk space.

In that situation, right now, as of today, the right thing to do is:

	- stop being stubborn
	- pick an active file
	- copy it somewhere else
	- remove it
	- run snap -a to archive blocks to Venti,
		hopefully freeing most of the disk
	- copy the file back

You can *always* do that.

Russ