From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <205f210f9eb4f053e224dab1216b8952@tombob.com> To: rminnich@lanl.gov, 9fans@cse.psu.edu Subject: Re: [9fans] simple venti question. From: plan9@blueyonder.co.uk In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Wed, 4 Feb 2004 10:11:43 +0000 Topicbox-Message-UUID: cd613990-eacc-11e9-9e20-41e7f4b1d025 > - dead fossil (filled up, can't boot the machine at this point as fossil > is full -- not sure yet why this keeps happening ...) You probably haven't set up snapshot timeouts for your fossil. From fossilcons(8): ... [ fsys name ] snaptime [ -a hhmm ] [ -s interval ] [ -t timeout ] ... Snaptime displays and edits the times at which snapshots are automatically taken. An archival snapshot is taken once a day, at hhmm, while temporary snapshots are taken at multi- ples of interval minutes. Temporary snapshots are discarded once they are timeout minutes old. With no arguments, snaptime prints the current snapshot times. The -a and -s options set the archive and snapshot times. An hhmm or interval of `none' can be used to disable that kind of auto- matic snapshot. The -t option sets the snapshot timeout. If timeout is `none', temporary snapshots are not automati- cally discarded. By default, all three times are set to `none'. ... Without that, your fossil will fill up with as many snapshots as fit. I believe you can make space in your fossil by using the epoch fossilcons command. But the proper way is to set up a timeout for it to discard old snapshots. When this happened to me ages ago, I was able to boot using my old kfs partition and then start the fossil manually (it wasn't able to serve files, but the my fscons was available), connect to its console, use epoch to clear some space and finally boot using fossil again. Hope this helps, Robby