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: Tue, 5 Mar 2013 23:01:01 +0900 [thread overview]
Message-ID: <62CFB779-38F2-4577-BB28-625AEBD2F1C1@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <BF86FE5E-4EA3-4330-BA78-4DAC6F632CC3@ar.aichi-u.ac.jp>
Hello,
I reconsidered my problem. I said:
> corresponding worm blocks of dirty cache blocks are garbage.
now I think, this is not a problem. this is a state that it should be.
the problem is only in the fact: my dirty blocks wouldn't be dumped.
next prev parent reply other threads:[~2013-03-05 14:01 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 [this message]
2013-03-05 14:04 ` erik quanstrom
2013-03-06 12:48 ` arisawa
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=62CFB779-38F2-4577-BB28-625AEBD2F1C1@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).