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 ;-)
Please note that I won't read my mails until next saturday morning (CEST).
After disconnection of iSCSI target :
Tasks: 232 total, 7 running, 224 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.0%us, 15.2%sy, 0.0%ni, 84.3%id, 0.0%wa, 0.1%hi, 0.3%si,
0.0%st
Mem: 4139032k total, 4127584k used, 11448k free, 95752k buffers
Swap: 7815536k total, 0k used, 7815536k free, 3758792k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9738 root 15 -5 0 0 0 R 100 0.0 4:56.82 md_d0_raid5
9774 root 15 -5 0 0 0 R 100 0.0 5:52.41 istd1
9739 root 15 -5 0 0 0 R 14 0.0 0:28.90 md_d0_resync
9916 root 20 0 3248 1544 1120 R 2 0.0 0:00.56 top
4129 root 20 0 41648 5024 2432 S 0 0.1 2:56.17
fail2ban-server
1 root 20 0 2576 960 816 S 0 0.0 0:01.58 init
2 root 15 -5 0 0 0 S 0 0.0 0:00.00 kthreadd
3 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/0
4 root 15 -5 0 0 0 S 0 0.0 0:00.02 ksoftirqd/0
5 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/1
6 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksoftirqd/1
Regards,
JKB
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
