From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dirty blocks in cwfs
Date: Wed, 6 Mar 2013 21:48:50 +0900 [thread overview]
Message-ID: <65D43A00-7F64-461A-B021-1B912C63AE4E@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <c19ec7dd802d2f6446e126d59efc4885@kw.quanstro.net>
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,
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.
next prev parent reply other threads:[~2013-03-06 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 6:02 arisawa
2013-03-05 6:22 ` erik quanstrom
2013-03-05 8:55 ` arisawa
2013-03-05 14:01 ` arisawa
2013-03-05 14:04 ` erik quanstrom
2013-03-06 12:48 ` arisawa [this message]
2013-03-09 23:14 ` cinap_lenrek
2013-03-10 1:34 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65D43A00-7F64-461A-B021-1B912C63AE4E@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).