From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 12 Jan 2012 22:29:19 +0100
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Message-ID: <20120112222919.0bb0c261@gmail.com>
In-Reply-To: <20120113183323.GA971@polynum.com>
References: <20120110024048.GA407@polynum.com>
	<20120109232333.1d847e92@gmail.com>
	<20120110171129.GD344@polynum.com>
	<20120110144719.2c67cd9e@wks-ddc.exosec.local>
	<20120113183323.GA971@polynum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] fossil (again)
Topicbox-Message-UUID: 59aac894-ead7-11e9-9d60-3106f5b1d025

> So, there is no snapshot, only plan9.iso + apx. 40Mb for kerTeX, /tmp
> empty, and I still have almost 750 Mb used and only 220Mb free?
>
> Is there a way to know what occupies roughly twice the size of the
> files?

I don't know. I just set up a tiny Fossil file system and
extracted the current Plan 9 CD image on it:

term% du -sh plan9.iso
276.5566M	plan9.iso

main: df
main: 397,328,384 used + 674,422,784 free = 1,071,751,168 (37% used)

> Furthermore, fossil/flchk is "deprecated in favor of console", but
> should work, and does not because there is no venti. (on console,
> check reports no leak and no problem)

Use fossil/flchk -f when Fossil is not connected to Venti.

You should not use fossil/flchk to fix a running Fossil.
The "check" command from the Fossil console is safe
because it halts Fossil before running the check and
unhalts it after.

> Anybody having ideas how to debug? Unless the 8kb default blocksize
> for the distribution explains the overhead... But that seems to me a
> bit too much!

You should probably try to compare with "du -sh".

--
David du Colombier