linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	linux-raid@vger.kernel.org, sparclinux@vger.kernel.org,
	iscsitarget-devel@lists.sourceforge.net
Subject: Re: [BUG] Raid1/5 over iSCSI trouble
Date: Sat, 20 Oct 2007 09:52:17 +0200	[thread overview]
Message-ID: <4719B3B1.90509@systella.fr> (raw)
In-Reply-To: <471942D2.3070609@tmr.com>

Bill Davidsen wrote:
> BERTRAND Joël wrote:
>>
>>     Sorry for this last mail. I have found another mistake, but I 
>> don't know if this bug comes from iscsi-target or raid5 itself. iSCSI 
>> target is disconnected because istd1 and md_d0_raid5 kernel threads 
>> use 100% of CPU each !
>>
>> Tasks: 235 total,   6 running, 227 sleeping,   0 stopped,   2 zombie
>> Cpu(s):  0.1%us, 12.5%sy,  0.0%ni, 87.4%id,  0.0%wa,  0.0%hi,  0.0%si, 
>> 0.0%st
>> Mem:   4139032k total,   218424k used,  3920608k free,    10136k buffers
>> Swap:  7815536k total,        0k used,  7815536k free,    64808k cached
>>
>>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>>  5824 root      15  -5     0    0    0 R  100  0.0  10:34.25 istd1
>>  5599 root      15  -5     0    0    0 R  100  0.0   7:25.43 md_d0_raid5
> 
> Given that the summary shows 87.4% idle, something is not right. You 
> might try another tool, like vmstat, to at least verify the way the CPU 
> is being used. When you can't trust what your tools tell you it gets 
> really hard to make decisions based on the data.

	Don't forget this box is a 32-CPU server.

	JKB
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2007-10-20  7:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 13:24 [BUG] Raid5 trouble BERTRAND Joël
2007-10-17 14:32 ` BERTRAND Joël
2007-10-17 14:58   ` Dan Williams
2007-10-17 15:40     ` Dan Williams
2007-10-17 16:44       ` BERTRAND Joël
2007-10-18  0:46         ` Dan Williams
2007-10-18  8:29           ` BERTRAND Joël
2007-10-19  2:55       ` Bill Davidsen
2007-10-19  8:04         ` BERTRAND Joël
2007-10-19 15:51           ` Dan Williams
2007-10-19 16:03             ` BERTRAND Joël
     [not found]             ` <4718DE66.8000905@tmr.com>
2007-10-19 20:42               ` BERTRAND Joël
2007-10-19 20:49                 ` [BUG] Raid1/5 over iSCSI trouble BERTRAND Joël
2007-10-19 21:02                   ` [Iscsitarget-devel] " Ross S. W. Walker
2007-10-19 21:06                     ` BERTRAND Joël
2007-10-19 21:10                       ` Ross S. W. Walker
2007-10-20  7:45                         ` BERTRAND Joël
2007-10-19 21:11                       ` [Iscsitarget-devel] " Scott Kaelin
2007-10-19 21:04                   ` BERTRAND Joël
2007-10-19 21:08                     ` Ross S. W. Walker
2007-10-19 21:12                     ` Dan Williams
2007-10-20  8:05                       ` BERTRAND Joël
2007-10-24  7:12                         ` BERTRAND Joël
2007-10-24 20:10                           ` Bill Davidsen
2007-10-24 23:49                           ` Dan Williams
2007-10-25  0:03                             ` David Miller
2007-10-27 13:29                             ` BERTRAND Joël
2007-10-27 18:27                               ` Dan Williams
2007-10-27 19:35                                 ` BERTRAND Joël
2007-10-27 21:13                               ` Ming Zhang
2007-10-29 10:40                                 ` BERTRAND Joël
2007-10-19 21:19                     ` Ming Zhang
2007-10-19 23:50                     ` Bill Davidsen
2007-10-19 23:58                       ` Bill Davidsen
2007-10-20  7:52                       ` BERTRAND Joël [this message]
2007-10-17 16:07     ` [BUG] Raid5 trouble BERTRAND Joël

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=4719B3B1.90509@systella.fr \
    --to=joel.bertrand@systella.fr \
    --cc=dan.j.williams@intel.com \
    --cc=davidsen@tmr.com \
    --cc=iscsitarget-devel@lists.sourceforge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /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).