From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] checkarenas
Date: Thu, 16 Sep 2010 22:58:45 -0400 [thread overview]
Message-ID: <AANLkTi=zAc5MOjMJwNLjNS56=wuT2J=WCa6dHsMKDQyU@mail.gmail.com> (raw)
In-Reply-To: <BF59F2C9-9D10-4FE1-81D9-FD22910B67DF@ar.aichi-u.ac.jp>
> I noticed strange output that I can't understand.
I can't understand it either.
It doesn't make any sense to me.
It might be interesting to run
cpu -h io
iostats venti/checkarenas -v /dev/sdC0/arenas arena.30
and see if the problem happens then.
The only thing I can think of is that
when run with something proxying the
9p connection, some reads return
less than the amount of data requested,
and venti is not correctly reissuing
the read for the remainder of the block.
That's a very scary thought.
The relevant function is /sys/src/cmd/venti/srv/part.c:/^prwb
but it looks okay. Maybe there is some
bit of code that's not calling it.
Russ
next prev parent reply other threads:[~2010-09-17 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 23:19 Kenji Arisawa
2010-09-17 2:58 ` Russ Cox [this message]
2010-09-17 22:33 ` Kenji Arisawa
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='AANLkTi=zAc5MOjMJwNLjNS56=wuT2J=WCa6dHsMKDQyU@mail.gmail.com' \
--to=rsc@swtch.com \
--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).