From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Corrupted meta data
Date: Thu, 17 Jul 2008 18:40:45 +0000 [thread overview]
Message-ID: <071720081840.19971.487F922D00083BF900004E0322218865869B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <20080717161750.8A30B1E8C1C@holo.morphisms.net>
> It's more likely in a bad loop somewhere.
> Is it repeatedly doing I/O during the 100% cpu?
It just locked again. Here's what I'm seeing. In
top, the first thread is using 100% of the CPU and
all the other threads are in the S state with no run
time. I don't see any indications either in vmstat
or in load from p9p that there is any I/O going
on to speak of or an unusual number of system calls
being issued. If there's anything else I can
check, let me know.
Thanks,
BLS
prev parent reply other threads:[~2008-07-17 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:25 Brian L. Stuart
2008-07-16 22:01 ` Russ Cox
2008-07-17 15:39 ` Brian L. Stuart
2008-07-17 16:20 ` Russ Cox
2008-07-17 17:56 ` Brian L. Stuart
2008-07-17 18:40 ` Brian L. Stuart [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=071720081840.19971.487F922D00083BF900004E0322218865869B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.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).