9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] df for fossil?
Date: Tue, 14 Jan 2003 11:10:29 -0500	[thread overview]
Message-ID: <645393765206d0ff808837fb7cea1632@plan9.bell-labs.com> (raw)
In-Reply-To: <93b0889692ef974561c174f7b857b343@plan9.escet.urjc.es>

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



  reply	other threads:[~2003-01-14 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  9:12 Fco.J.Ballesteros
2003-01-14 12:52 ` Russ Cox
2003-01-14 13:23   ` Russ Cox
2003-01-14 14:57   ` Fco.J.Ballesteros
2003-01-14 15:06     ` Russ Cox
2003-01-14 15:34       ` Fco.J.Ballesteros
2003-01-14 15:48         ` Russ Cox
2003-01-14 15:57           ` Fco.J.Ballesteros
2003-01-14 16:10             ` Russ Cox [this message]
2003-01-14 16:16               ` Fco.J.Ballesteros

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=645393765206d0ff808837fb7cea1632@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --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).