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 15:29:27 +0200 [thread overview]
Message-ID: <47233D37.6070409@systella.fr> (raw)
In-Reply-To: <e9c3a7c20710241649qb26c36by5733a93cff394c40@mail.gmail.com>
Dan Williams wrote:
> On 10/24/07, BERTRAND Joël <joel.bertrand@systella.fr> wrote:
>> Hello,
>>
>> Any news about this trouble ? Any idea ? I'm trying to fix it, but I
>> don't see any specific interaction between raid5 and istd. Does anyone
>> try to reproduce this bug on another arch than sparc64 ? I only use
>> sparc32 and 64 servers and I cannot test on other archs. Of course, I
>> have a laptop, but I cannot create a raid5 array on its internal HD to
>> test this configuration ;-)
>>
>
> 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.
Profiling through timer interrupt
samples % image name app name
symbol name
20028038 92.9510 vmlinux-2.6.23 vmlinux-2.6.23 cpu_idle
1198566 5.5626 vmlinux-2.6.23 vmlinux-2.6.23 schedule
41558 0.1929 vmlinux-2.6.23 vmlinux-2.6.23 yield
34791 0.1615 vmlinux-2.6.23 vmlinux-2.6.23 NGmemcpy
18417 0.0855 vmlinux-2.6.23 vmlinux-2.6.23
xor_niagara_5
17430 0.0809 raid456 raid456 (no
symbols)
15837 0.0735 vmlinux-2.6.23 vmlinux-2.6.23
sys_sched_yield
14860 0.0690 iscsi_trgt.ko iscsi_trgt istd
12705 0.0590 nf_conntrack nf_conntrack (no
symbols)
9236 0.0429 libc-2.6.1.so libc-2.6.1.so (no
symbols)
9034 0.0419 vmlinux-2.6.23 vmlinux-2.6.23
xor_niagara_2
6534 0.0303 oprofiled oprofiled (no
symbols)
6149 0.0285 vmlinux-2.6.23 vmlinux-2.6.23
scsi_request_fn
5947 0.0276 ip_tables ip_tables (no
symbols)
4510 0.0209 vmlinux-2.6.23 vmlinux-2.6.23
dma_4v_map_single
3823 0.0177 vmlinux-2.6.23 vmlinux-2.6.23
__make_request
3326 0.0154 vmlinux-2.6.23 vmlinux-2.6.23 tg3_poll
3162 0.0147 iscsi_trgt.ko iscsi_trgt
scsi_cmnd_exec
3091 0.0143 vmlinux-2.6.23 vmlinux-2.6.23
scsi_dispatch_cmd
2849 0.0132 vmlinux-2.6.23 vmlinux-2.6.23
tcp_v4_rcv
2811 0.0130 vmlinux-2.6.23 vmlinux-2.6.23
nf_iterate
2729 0.0127 vmlinux-2.6.23 vmlinux-2.6.23
_spin_lock_bh
2551 0.0118 vmlinux-2.6.23 vmlinux-2.6.23 kfree
2467 0.0114 vmlinux-2.6.23 vmlinux-2.6.23
kmem_cache_free
2314 0.0107 vmlinux-2.6.23 vmlinux-2.6.23
atomic_add
2065 0.0096 vmlinux-2.6.23 vmlinux-2.6.23
NGbzero_loop
1826 0.0085 vmlinux-2.6.23 vmlinux-2.6.23 ip_rcv
1823 0.0085 nf_conntrack_ipv4 nf_conntrack_ipv4 (no
symbols)
1822 0.0085 vmlinux-2.6.23 vmlinux-2.6.23
clear_bit
1767 0.0082 python2.4 python2.4 (no
symbols)
1734 0.0080 vmlinux-2.6.23 vmlinux-2.6.23
atomic_sub_ret
1694 0.0079 vmlinux-2.6.23 vmlinux-2.6.23
tcp_rcv_established
1673 0.0078 vmlinux-2.6.23 vmlinux-2.6.23
tcp_recvmsg
1670 0.0078 vmlinux-2.6.23 vmlinux-2.6.23
netif_receive_skb
1668 0.0077 vmlinux-2.6.23 vmlinux-2.6.23 set_bit
1545 0.0072 vmlinux-2.6.23 vmlinux-2.6.23
__kmalloc_track_caller
1526 0.0071 iptable_nat iptable_nat (no
symbols)
1526 0.0071 vmlinux-2.6.23 vmlinux-2.6.23
kmem_cache_alloc
1373 0.0064 vmlinux-2.6.23 vmlinux-2.6.23
generic_unplug_device
...
Is it enough ?
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 13:29:27 +0000 [thread overview]
Message-ID: <47233D37.6070409@systella.fr> (raw)
In-Reply-To: <e9c3a7c20710241649qb26c36by5733a93cff394c40@mail.gmail.com>
Dan Williams wrote:
> On 10/24/07, BERTRAND Joël <joel.bertrand@systella.fr> wrote:
>> Hello,
>>
>> Any news about this trouble ? Any idea ? I'm trying to fix it, but I
>> don't see any specific interaction between raid5 and istd. Does anyone
>> try to reproduce this bug on another arch than sparc64 ? I only use
>> sparc32 and 64 servers and I cannot test on other archs. Of course, I
>> have a laptop, but I cannot create a raid5 array on its internal HD to
>> test this configuration ;-)
>>
>
> 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.
Profiling through timer interrupt
samples % image name app name
symbol name
20028038 92.9510 vmlinux-2.6.23 vmlinux-2.6.23 cpu_idle
1198566 5.5626 vmlinux-2.6.23 vmlinux-2.6.23 schedule
41558 0.1929 vmlinux-2.6.23 vmlinux-2.6.23 yield
34791 0.1615 vmlinux-2.6.23 vmlinux-2.6.23 NGmemcpy
18417 0.0855 vmlinux-2.6.23 vmlinux-2.6.23
xor_niagara_5
17430 0.0809 raid456 raid456 (no
symbols)
15837 0.0735 vmlinux-2.6.23 vmlinux-2.6.23
sys_sched_yield
14860 0.0690 iscsi_trgt.ko iscsi_trgt istd
12705 0.0590 nf_conntrack nf_conntrack (no
symbols)
9236 0.0429 libc-2.6.1.so libc-2.6.1.so (no
symbols)
9034 0.0419 vmlinux-2.6.23 vmlinux-2.6.23
xor_niagara_2
6534 0.0303 oprofiled oprofiled (no
symbols)
6149 0.0285 vmlinux-2.6.23 vmlinux-2.6.23
scsi_request_fn
5947 0.0276 ip_tables ip_tables (no
symbols)
4510 0.0209 vmlinux-2.6.23 vmlinux-2.6.23
dma_4v_map_single
3823 0.0177 vmlinux-2.6.23 vmlinux-2.6.23
__make_request
3326 0.0154 vmlinux-2.6.23 vmlinux-2.6.23 tg3_poll
3162 0.0147 iscsi_trgt.ko iscsi_trgt
scsi_cmnd_exec
3091 0.0143 vmlinux-2.6.23 vmlinux-2.6.23
scsi_dispatch_cmd
2849 0.0132 vmlinux-2.6.23 vmlinux-2.6.23
tcp_v4_rcv
2811 0.0130 vmlinux-2.6.23 vmlinux-2.6.23
nf_iterate
2729 0.0127 vmlinux-2.6.23 vmlinux-2.6.23
_spin_lock_bh
2551 0.0118 vmlinux-2.6.23 vmlinux-2.6.23 kfree
2467 0.0114 vmlinux-2.6.23 vmlinux-2.6.23
kmem_cache_free
2314 0.0107 vmlinux-2.6.23 vmlinux-2.6.23
atomic_add
2065 0.0096 vmlinux-2.6.23 vmlinux-2.6.23
NGbzero_loop
1826 0.0085 vmlinux-2.6.23 vmlinux-2.6.23 ip_rcv
1823 0.0085 nf_conntrack_ipv4 nf_conntrack_ipv4 (no
symbols)
1822 0.0085 vmlinux-2.6.23 vmlinux-2.6.23
clear_bit
1767 0.0082 python2.4 python2.4 (no
symbols)
1734 0.0080 vmlinux-2.6.23 vmlinux-2.6.23
atomic_sub_ret
1694 0.0079 vmlinux-2.6.23 vmlinux-2.6.23
tcp_rcv_established
1673 0.0078 vmlinux-2.6.23 vmlinux-2.6.23
tcp_recvmsg
1670 0.0078 vmlinux-2.6.23 vmlinux-2.6.23
netif_receive_skb
1668 0.0077 vmlinux-2.6.23 vmlinux-2.6.23 set_bit
1545 0.0072 vmlinux-2.6.23 vmlinux-2.6.23
__kmalloc_track_caller
1526 0.0071 iptable_nat iptable_nat (no
symbols)
1526 0.0071 vmlinux-2.6.23 vmlinux-2.6.23
kmem_cache_alloc
1373 0.0064 vmlinux-2.6.23 vmlinux-2.6.23
generic_unplug_device
...
Is it enough ?
Regards,
JKB
next prev parent reply other threads:[~2007-10-27 13:29 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 [this message]
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
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=47233D37.6070409@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.