From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-raid@vger.kernel.org, sparclinux@vger.kernel.org,
iscsitarget-devel@lists.sourceforge.net
Subject: Re: [BUG] Raid1/5 over iSCSI trouble
Date: Wed, 24 Oct 2007 09:12:58 +0200 [thread overview]
Message-ID: <471EF07A.5040007@systella.fr> (raw)
In-Reply-To: <4719B6DE.9040403@systella.fr>
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
next prev parent reply other threads:[~2007-10-24 7:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:24 [BUG] Raid5 trouble BERTRAND Joël
2007-10-17 14:32 ` BERTRAND Joël
2007-10-17 14:58 ` Dan Williams
2007-10-17 15:40 ` Dan Williams
2007-10-17 16:44 ` BERTRAND Joël
2007-10-18 0:46 ` Dan Williams
2007-10-18 8:29 ` BERTRAND Joël
2007-10-19 2:55 ` Bill Davidsen
2007-10-19 8:04 ` BERTRAND Joël
2007-10-19 15:51 ` Dan Williams
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:49 ` [BUG] Raid1/5 over iSCSI trouble BERTRAND Joël
2007-10-19 21:02 ` [Iscsitarget-devel] " Ross S. W. Walker
2007-10-19 21:06 ` BERTRAND Joël
2007-10-19 21:10 ` Ross S. W. Walker
2007-10-20 7:45 ` BERTRAND Joël
2007-10-19 21:11 ` [Iscsitarget-devel] " Scott Kaelin
2007-10-19 21:04 ` BERTRAND Joël
2007-10-19 21:08 ` Ross S. W. Walker
2007-10-19 21:12 ` Dan Williams
2007-10-20 8:05 ` BERTRAND Joël
2007-10-24 7:12 ` BERTRAND Joël [this message]
2007-10-24 20:10 ` Bill Davidsen
2007-10-24 23:49 ` Dan Williams
2007-10-25 0:03 ` David Miller
2007-10-27 13:29 ` BERTRAND Joël
2007-10-27 18:27 ` Dan Williams
2007-10-27 19:35 ` BERTRAND Joël
2007-10-27 21:13 ` Ming Zhang
2007-10-29 10:40 ` BERTRAND Joël
2007-10-19 21:19 ` Ming Zhang
2007-10-19 23:50 ` Bill Davidsen
2007-10-19 23:58 ` Bill Davidsen
2007-10-20 7:52 ` BERTRAND Joël
2007-10-17 16:07 ` [BUG] Raid5 trouble 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=471EF07A.5040007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).