From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <40B2738E.70306@chunder.com> Date: Tue, 25 May 2004 08:13:34 +1000 From: Bruce Ellis User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] fossil question References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 86cb6162-eacd-11e9-9e20-41e7f4b1d025 how can this work if fossil is main and it's full (as it is now, though i've done no work since last mail)? aren't i overwriting an active filesystem that contains the pages of everything executing? i hope i don't have to do this every second month. the "slow" leak is a bit too fast for me. brucee Russ Cox wrote: > The best thing about fossil is snap -a. If it gets to the point > where you've leaked away your entire disk (which seems to > happen very slowly), record the snap, use vacfs to double-check > that your data and dumps are there, and then run the bfree > commands. The disk is just a write buffer, so as long as > everything shows up in vacfs, you can't destroy anything > important. If the worst happens (very unlikely) you can always > flfmt with the snap -a score. > > Russ