All of lore.kernel.org
 help / color / mirror / Atom feed
From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, sparclinux@vger.kernel.org,
	iscsitarget-devel@lists.sourceforge.net,
	Bill Davidsen <davidsen@tmr.com>
Subject: Re: [BUG] Raid1/5 over iSCSI trouble
Date: Sat, 27 Oct 2007 21:35:44 +0200	[thread overview]
Message-ID: <47239310.6060801@systella.fr> (raw)
In-Reply-To: <e9c3a7c20710271127p24635207p4b5cc03047118f36@mail.gmail.com>

Dan Williams wrote:
> On 10/27/07, BERTRAND Joël <joel.bertrand@systella.fr> wrote:
>> Dan Williams wrote:
>>> Can you collect some oprofile data, as Ming suggested, so we can maybe
>>> see what md_d0_raid5 and istd1 are fighting about?  Hopefully it is as
>>> painless to run on sparc as it is on IA:
>>>
>>> opcontrol --start --vmlinux=/path/to/vmlinux
>>> <wait>
>>> opcontrol --stop
>>> opreport --image-path=/lib/modules/`uname -r` -l
>>         Done.
>>
> 
> [..]
> 
>>         Is it enough ?
> 
> I would expect md_d0_raid5 and istd1 to show up pretty high in the
> list if they are constantly pegged at a 100% CPU utilization like you
> showed in the failure case.  Maybe this was captured after the target
> has disconnected?

	No, I have launched opcontrol before starting raid1 creation, and 
stopped after disconnection. Don't forget that this server has 32 CPU's.

	Regards,

	JKB

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

WARNING: multiple messages have this Message-ID (diff)
From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, sparclinux@vger.kernel.org,
	iscsitarget-devel@lists.sourceforge.net,
	Bill Davidsen <davidsen@tmr.com>
Subject: Re: [BUG] Raid1/5 over iSCSI trouble
Date: Sat, 27 Oct 2007 19:35:44 +0000	[thread overview]
Message-ID: <47239310.6060801@systella.fr> (raw)
In-Reply-To: <e9c3a7c20710271127p24635207p4b5cc03047118f36@mail.gmail.com>

Dan Williams wrote:
> On 10/27/07, BERTRAND Joël <joel.bertrand@systella.fr> wrote:
>> Dan Williams wrote:
>>> Can you collect some oprofile data, as Ming suggested, so we can maybe
>>> see what md_d0_raid5 and istd1 are fighting about?  Hopefully it is as
>>> painless to run on sparc as it is on IA:
>>>
>>> opcontrol --start --vmlinux=/path/to/vmlinux
>>> <wait>
>>> opcontrol --stop
>>> opreport --image-path=/lib/modules/`uname -r` -l
>>         Done.
>>
> 
> [..]
> 
>>         Is it enough ?
> 
> I would expect md_d0_raid5 and istd1 to show up pretty high in the
> list if they are constantly pegged at a 100% CPU utilization like you
> showed in the failure case.  Maybe this was captured after the target
> has disconnected?

	No, I have launched opcontrol before starting raid1 creation, and 
stopped after disconnection. Don't forget that this server has 32 CPU's.

	Regards,

	JKB

  reply	other threads:[~2007-10-27 19:35 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 13:24 [BUG] Raid5 trouble BERTRAND Joël
2007-10-16 13:24 ` BERTRAND Joël
2007-10-17 14:32 ` BERTRAND Joël
2007-10-17 14:32   ` BERTRAND Joël
2007-10-17 14:58   ` Dan Williams
2007-10-17 14:58     ` Dan Williams
2007-10-17 15:40     ` Dan Williams
2007-10-17 15:40       ` Dan Williams
2007-10-17 16:44       ` BERTRAND Joël
2007-10-17 16:44         ` BERTRAND Joël
2007-10-18  0:46         ` Dan Williams
2007-10-18  0:46           ` Dan Williams
2007-10-18  8:29           ` BERTRAND Joël
2007-10-18  8:29             ` BERTRAND Joël
2007-10-19  2:55       ` Bill Davidsen
2007-10-19  2:55         ` Bill Davidsen
2007-10-19  8:04         ` BERTRAND Joël
2007-10-19  8:04           ` BERTRAND Joël
2007-10-19 15:51           ` Dan Williams
2007-10-19 15:51             ` Dan Williams
2007-10-19 16:03             ` BERTRAND Joël
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:42                 ` BERTRAND Joël
2007-10-19 20:49                 ` [BUG] Raid1/5 over iSCSI trouble BERTRAND Joël
2007-10-19 20:49                   ` BERTRAND Joël
2007-10-19 21:02                   ` [Iscsitarget-devel] " Ross S. W. Walker
2007-10-19 21:02                     ` Ross S. W. Walker
2007-10-19 21:06                     ` BERTRAND Joël
2007-10-19 21:06                       ` [Iscsitarget-devel] " BERTRAND Joël
2007-10-19 21:10                       ` Ross S. W. Walker
2007-10-19 21:10                         ` [Iscsitarget-devel] " Ross S. W. Walker
2007-10-20  7:45                         ` BERTRAND Joël
2007-10-20  7:45                           ` [Iscsitarget-devel] " BERTRAND Joël
2007-10-19 21:11                       ` Scott Kaelin
2007-10-19 21:11                         ` Scott Kaelin
2007-10-19 21:04                   ` BERTRAND Joël
2007-10-19 21:04                     ` BERTRAND Joël
2007-10-19 21:08                     ` Ross S. W. Walker
2007-10-19 21:08                       ` [Iscsitarget-devel] " Ross S. W. Walker
2007-10-19 21:12                     ` Dan Williams
2007-10-19 21:12                       ` Dan Williams
2007-10-20  8:05                       ` BERTRAND Joël
2007-10-20  8:05                         ` BERTRAND Joël
2007-10-24  7:12                         ` BERTRAND Joël
2007-10-24  7:12                           ` BERTRAND Joël
2007-10-24 20:10                           ` Bill Davidsen
2007-10-24 20:10                             ` Bill Davidsen
2007-10-24 23:49                           ` Dan Williams
2007-10-24 23:49                             ` Dan Williams
2007-10-25  0:03                             ` David Miller
2007-10-25  0:03                               ` David Miller
2007-10-27 13:29                             ` BERTRAND Joël
2007-10-27 13:29                               ` BERTRAND Joël
2007-10-27 18:27                               ` Dan Williams
2007-10-27 18:27                                 ` Dan Williams
2007-10-27 19:35                                 ` BERTRAND Joël [this message]
2007-10-27 19:35                                   ` BERTRAND Joël
2007-10-27 21:13                               ` Ming Zhang
2007-10-27 21:13                                 ` Ming Zhang
2007-10-29 10:40                                 ` BERTRAND Joël
2007-10-29 10:40                                   ` BERTRAND Joël
2007-10-19 21:19                     ` Ming Zhang
2007-10-19 21:19                       ` [Iscsitarget-devel] " Ming Zhang
2007-10-19 23:50                     ` Bill Davidsen
2007-10-19 23:50                       ` Bill Davidsen
2007-10-19 23:58                       ` Bill Davidsen
2007-10-19 23:58                         ` Bill Davidsen
2007-10-20  7:52                       ` BERTRAND Joël
2007-10-20  7:52                         ` BERTRAND Joël
2007-10-17 16:07     ` [BUG] Raid5 trouble BERTRAND Joël
2007-10-17 16:07       ` 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=47239310.6060801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.