Dan Williams wrote:
On 10/27/07, BERTRAND Joël <[EMAIL PROTECTED]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
