From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <40B13E50.3010908@chunder.com>
Date: Mon, 24 May 2004 10:14:08 +1000
From: Bruce Ellis <brucee@chunder.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
MIME-Version: 1.0
To: "9fans@cse.psu.edu" <9fans@cse.psu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [9fans] fossil question
Topicbox-Message-UUID: 85a3b4c4-eacd-11e9-9e20-41e7f4b1d025

does fossil leak?

*caveat* i am not running the current version
so this may have been fixed.

my fossil has passed 90% full even though it
shouldn't have much more data in it than when
it was 20% full.

i have ...

	snaptime -a 0030 -s 30 -t 1440

which i believe means "snap -a at 0030,
snap every 30 minutes, and discard them
after a day".

if i run "fossil/flchk -f" i get thousands of
bfrees which all belong to long gone epochs.
i'm very reluctant to do an update as fossil
is the root filesystem and if i screw it up
i'm screwed - i'm also reluctant to do a few
thousand bfrees.

any help welcome.

brucee

PS "epoch" seems to always show more than a day's
snaps, sometimes a few days.  what's that all about?