linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: Unbalanced reads of RAID10
Date: Wed, 02 Sep 2009 12:13:15 -0400	[thread overview]
Message-ID: <4A9E999B.8070401@tmr.com> (raw)
In-Reply-To: <20090830003706.GB5633@rap.rap.dk>

Keld Jørn Simonsen wrote:
> On Sun, Aug 23, 2009 at 04:24:39PM +0200, Piergiorgio Sartor wrote:
>   
>> Hi all,
>>
>> some time ago I was reporting about a strange issue.
>>
>> I have a two HDDs system, with a small RAID1 (/boot)
>> and the rest as RAID10 f2 (with LVM on top).
>>
>> It seems that /dev/sdb has more reads than /dev/sda.
>>
>> I had a quick check, with "iostat", and it seems that
>> all small reads, somehow below 1~4KiB, are done from
>> /dev/sdb2, regardless.
>> Actually, it seems that only if there is a pending
>> (small) read, this will be scheduled to /dev/sda2,
>> but non-overlapping small reads seem to happen always
>> from /dev/sdb2.
>>
>> This occurs with the RAID10, but it seems also with
>> the RAID1.
>>     
>
> Hmm, have you done testing separately on each array?
>
>   
>> In normal operation, this does not seem to lead to
>> problems, but during the smart long test /dev/sdb
>> takes by far more time than /dev/sda, since each
>> small read stop the test, and small read occurs
>> whenever there is a small write from syslog or
>> similar.
>> Note that failing and removing /dev/sdb2 results
>> in much shorter time for the smart test, about
>> 1hr30min vs. the 6~7hrs with the drive still
>> attached to RAID10.
>>
>> Is there any way to tune which is the "preferred"
>> drive or the "preferred" policy in case of these
>> small (or big) reads?
>>     
>
> What level of the kernel are you running?
>
>   
>> Could this be due to HW configuration?
>> The two HDDs are numbered SATA1 and SATA2 in BIOS,
>> there are still SATA3 and SATA4 ports somehow
>> available (SATA3 has a DVD).
>>
>> How are the reads scheduled withing the RAID10 software?
>>     
>
> there was a change of this about 2.6.25 which forced reads to always be
> from the faster inner part of the disks, and that should even out reads.
>   

??? what faster inner part is that? The linear velocity and 
bytes/cylinder are higher as the diameter increases.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"Now we have another quarterback besides Kurt Warner telling us during postgame
interviews that he owes every great thing that happens to him on a football
field to his faith in Jesus. I knew there had to be a reason why the Almighty
included a mute button on my remote."
			-- Arthur Troyer on Tim Tebow (Sports Illustrated)


--
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

  reply	other threads:[~2009-09-02 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23 14:24 Unbalanced reads of RAID10 Piergiorgio Sartor
2009-08-30  0:37 ` Keld Jørn Simonsen
2009-09-02 16:13   ` Bill Davidsen [this message]
2009-09-02 21:27     ` Keld Jørn Simonsen

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=4A9E999B.8070401@tmr.com \
    --to=davidsen@tmr.com \
    --cc=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    /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).