Re: [BUG] Raid1/5 over iSCSI trouble

[Bill Davidsen <davidsen@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.
>
ALSO: you have zombie processes. Looking at machines up for 45, 54, and 
470 days, zombies are *not* something you just have to expect. Do you 
get these just about the same time things go to hell? Better you than 
me, I suspect there are still many ways to have a "learning experience" 
with iSCSI.

Hope that and the summary confusion result in some useful data.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


-
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