From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] entire cache is busy, 999 dirty
Date: Mon, 1 Feb 2010 13:39:16 +0900 [thread overview]
Message-ID: <D188AE33-D70B-46F7-8985-77A8F4CAB237@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <ab783cb8d810f6f0963045b35fb54ad7@brasstown.quanstro.net>
Hello erik,
> are you running the latest version of fossil?
probably not.
I will refresh my file server.
Thanks
Kenji Arisawa
On 2010/02/01, at 2:22, erik quanstrom wrote:
>> My question is:
>> (a) where these messages come from? venti?
>
> fossil. (cache.c)
>
>> (b) what is the problem?
>> (c) how to fix?
>
> good question. are you running the latest
> version of fossil? if not, this could be caused by slow
> disk writes which could in turn be caused by the
> periodic bug that cinap_lenrek reported.
>
> the 999 number is also curious. one would
> expect that there are more than 999 blocks
> in the cache.
>
> - erik
>
prev parent reply other threads:[~2010-02-01 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 5:04 Kenji Arisawa
2010-01-31 17:22 ` erik quanstrom
2010-02-01 4:39 ` Kenji Arisawa [this message]
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=D188AE33-D70B-46F7-8985-77A8F4CAB237@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).