From: "Yiqiang Ding" <yqding@rasilient.com>
To: Jakob Oestergaard <jakob@unthought.net>, raid@ddx.a2000.nu
Cc: linux-raid@vger.kernel.org
Subject: Re: Is Read speed faster when 1 disk is failed on raid5 ?
Date: Mon, 28 Oct 2002 10:27:46 -0800 [thread overview]
Message-ID: <004e01c27eaf$b6c11940$707ba8c0@YQDING> (raw)
In-Reply-To: 20021022112401.GA26549@unthought.net
I had the similar result with IDE drives through hpt374 controller. Still
don't understand why a degraded system has better read performance.
YQ
----- Original Message -----
From: "Jakob Oestergaard" <jakob@unthought.net>
To: <raid@ddx.a2000.nu>
Cc: <linux-raid@vger.kernel.org>
Sent: Tuesday, October 22, 2002 3:24 AM
Subject: Re: Is Read speed faster when 1 disk is failed on raid5 ?
> On Tue, Oct 22, 2002 at 12:49:41PM +0200, raid@ddx.a2000.nu wrote:
> >
> > On Tue, 22 Oct 2002, Jakob Oestergaard wrote:
> >
> > > I didn't follow the beginning of this thread, sorry. Is this SCSI?
> >
> > Ide disks on 3ware 7850 using software raid5
>
> Ok. Odd.
>
> My first guess would be that it's some master/slave IDE issue - but you
> are probably running all your disks as masters (one disk per channel),
> right?
>
> Other than that... Well, if the parity information is intact, the disks
> would need to skip the parity blocks when the array is read from
> sequentially. With a degraded array, the reads are all contiguous on
> the disks - this could be a difference perhaps??
>
> What chunk size are you using? And can you try a chunk size that is an
> order of magnitude bigger or smaller? (might take some time to test
> this out).
>
> For example, if you use a 4k chunksize (I don't think you do, if my last
> guess holds), then try 128k. If you are using 64k or above (which,
> again, if I am guessing correctly, is probably more like what you're
> using), then try 4k.
>
> --
> ................................................................
> : jakob@unthought.net : And I see the elder races, :
> :.........................: putrid forms of man :
> : Jakob Østergaard : See him rise and claim the earth, :
> : OZ9ABN : his downfall is at hand. :
> :.........................:............{Konkhra}...............:
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-10-28 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02Oct22.043816edt.62658@gpu.utcc.utoronto.ca>
2002-10-22 9:58 ` Is Read speed faster when 1 disk is failed on raid5 ? raid
2002-10-22 10:45 ` Jakob Oestergaard
2002-10-22 10:49 ` raid
2002-10-22 11:24 ` Jakob Oestergaard
2002-10-28 18:27 ` Yiqiang Ding [this message]
2002-10-28 21:02 ` Jakob Oestergaard
2002-10-28 21:37 ` Yiqiang Ding
2002-10-29 0:30 ` Jakob Oestergaard
2002-10-29 21:05 ` Yiqiang Ding
2002-10-31 11:56 ` Jakob Oestergaard
2002-10-10 21:18 3ware 7500-12, bad write speed raid
2002-10-17 8:19 ` Is Read speed faster when 1 disk is failed on raid5 ? raid
2002-10-17 11:52 ` raid
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='004e01c27eaf$b6c11940$707ba8c0@YQDING' \
--to=yqding@rasilient.com \
--cc=jakob@unthought.net \
--cc=linux-raid@vger.kernel.org \
--cc=raid@ddx.a2000.nu \
/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).