9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dirty blocks in cwfs
Date: Tue,  5 Mar 2013 01:22:06 -0500	[thread overview]
Message-ID: <41f95d8dba3fa0a675fbc54e151ba844@kw.quanstro.net> (raw)
In-Reply-To: <7E48F293-1D27-4958-BB64-BDDC490CB7E7@ar.aichi-u.ac.jp>

On Tue Mar  5 01:03:23 EST 2013, arisawa@ar.aichi-u.ac.jp wrote:
> Hello,
>
> It seems my cwfs has too many dirty blocks.
> cfws command ("dump", "check tag" and etc) is no help to decrease these blocks.
> is this only to me?

i have not seen this with kenfs.  is it possible that you
are using the "t" bit that 9front added?  if so, that would
explain all the dirty blocks that never get dumped.
one also ends up with dirty superblocks that can't get
dumped because they're already written, about 1 per
day in the dump.

one thing i notice about your cache-worm is that the
cache is very large.  this is not advisable because your
cache buckets will take up too many memory buffers,
leaving little for actual data.  20G cache has been
enough.  the first big file server i set up had 750G
cache, and it thrashed the heck out of its disks.

- erik



  reply	other threads:[~2013-03-05  6:22 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 [this message]
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
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=41f95d8dba3fa0a675fbc54e151ba844@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).