From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Davidsen Subject: Re: [BUG] Raid1/5 over iSCSI trouble Date: Fri, 19 Oct 2007 19:50:42 -0400 Message-ID: <471942D2.3070609@tmr.com> References: <4714BB92.7040701@systella.fr> <47161CE3.80909@systella.fr> <47181CB2.1060602@tmr.com> <471864F8.9010209@systella.fr> <1192809103.30976.11.camel@dwillia2-linux.ch.intel.com> <4718DE66.8000905@tmr.com> <471916B5.6080709@systella.fr> <47191855.4020402@systella.fr> <47191BCF.2000908@systella.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <47191BCF.2000908@systella.fr> Sender: sparclinux-owner@vger.kernel.org To: =?UTF-8?B?QkVSVFJBTkQgSm/Dq2w=?= Cc: Dan Williams , linux-raid@vger.kernel.org, sparclinux@vger.kernel.org, iscsitarget-devel@lists.sourceforge.net List-Id: linux-raid.ids BERTRAND Jo=C3=ABl wrote: > > Sorry for this last mail. I have found another mistake, but I=20 > don't know if this bug comes from iscsi-target or raid5 itself. iSCSI= =20 > target is disconnected because istd1 and md_d0_raid5 kernel threads=20 > 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= ,=20 > 0.0%st > Mem: 4139032k total, 218424k used, 3920608k free, 10136k buff= ers > Swap: 7815536k total, 0k used, 7815536k free, 64808k cach= ed > > 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_ra= id5 Given that the summary shows 87.4% idle, something is not right. You=20 might try another tool, like vmstat, to at least verify the way the CPU= =20 is being used. When you can't trust what your tools tell you it gets=20 really hard to make decisions based on the data. --=20 bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 - To unsubscribe from this list: send the line "unsubscribe sparclinux" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Davidsen Date: Fri, 19 Oct 2007 23:50:42 +0000 Subject: Re: [BUG] Raid1/5 over iSCSI trouble Message-Id: <471942D2.3070609@tmr.com> List-Id: References: <4714BB92.7040701@systella.fr> <47161CE3.80909@systella.fr> <47181CB2.1060602@tmr.com> <471864F8.9010209@systella.fr> <1192809103.30976.11.camel@dwillia2-linux.ch.intel.com> <4718DE66.8000905@tmr.com> <471916B5.6080709@systella.fr> <47191855.4020402@systella.fr> <47191BCF.2000908@systella.fr> In-Reply-To: <47191BCF.2000908@systella.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: =?UTF-8?B?QkVSVFJBTkQgSm/Dq2w=?= Cc: Dan Williams , linux-raid@vger.kernel.org, sparclinux@vger.kernel.org, iscsitarget-devel@lists.sourceforge.net BERTRAND Jo=C3=ABl wrote: > > Sorry for this last mail. I have found another mistake, but I=20 > don't know if this bug comes from iscsi-target or raid5 itself. iSCSI=20 > target is disconnected because istd1 and md_d0_raid5 kernel threads=20 > 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,=20 > 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=20 might try another tool, like vmstat, to at least verify the way the CPU=20 is being used. When you can't trust what your tools tell you it gets=20 really hard to make decisions based on the data. --=20 bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979