Re: [9fans] df for fossil?

["Russ Cox" <rsc@plan9.bell-labs.com>]

> Keeping blocks reserved looks much better for me,
> since (for example, in my case) fossil can be your
> root file system, and you'll need to read it just to boot
> enough to recover it.

This doesn't make sense to me.

The only time you need blocks in reserve is when:

	- you are out of disk space
	- you have no snapshots to discard
	- you do not want to remove any data from the write buffer
	- you want to do an anonymous archival snapshot

If you mount the file system read-only you can *always*
read the whole thing.

Reserving two blocks on the disk for anonymous
archival snapshot roots would be sufficient to solve the problem:
you can be using at most one for the current file system root,
so at least one must be free (or at least, will be free once the
archiver finishes archiving that snapshot).

> By now I think I'll just make an emergency boot disk with
> that runs just the fossil console, to let me type without
> using the fossil.

I would just boot the bleeding edge sources CD.
Then you'd have a whole system at your disposal.

Russ