From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <c19ec7dd802d2f6446e126d59efc4885@kw.quanstro.net>
Date: Wed,  6 Mar 2013 21:48:50 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <65D43A00-7F64-461A-B021-1B912C63AE4E@ar.aichi-u.ac.jp>
References: <7E48F293-1D27-4958-BB64-BDDC490CB7E7@ar.aichi-u.ac.jp>
	<41f95d8dba3fa0a675fbc54e151ba844@kw.quanstro.net>
	<BF86FE5E-4EA3-4330-BA78-4DAC6F632CC3@ar.aichi-u.ac.jp>
	<62CFB779-38F2-4577-BB28-625AEBD2F1C1@ar.aichi-u.ac.jp>
	<c19ec7dd802d2f6446e126d59efc4885@kw.quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dirty blocks in cwfs
Topicbox-Message-UUID: 24a68dda-ead8-11e9-9d60-3106f5b1d025

Hello,

I have created dirty blocks that is not cleared by dump command.
the process is as follows:
(1) make a directory tree in somewhere.
	then we can observe these fscache blocks are in dirty state,=20
	as mentioned Geoff's documents.
(2) remove the tree using clri command.
        then we can confirm these fscache blocks still exist with dirty =
state.
(3) dump
(4) reboot
(5) we can again confirm these fscache blocks still exist with dirty =
state.

I have believed the dump command clears all dirty block in fscache,
however, it seems the command clears only dirty blocks that is =
referenced
by main tree.

FS(8) says:
 A subsequent check free will place the abandoned storage in the free =
list.

I did't "check free" immediately after clri.