From: Daniel Spannbauer <ds@marco.de>
To: linux-raid@vger.kernel.org
Subject: Re: Raid1: sdb has a lot mor work then sda
Date: Tue, 24 Apr 2012 17:02:49 +0200 [thread overview]
Message-ID: <4F96C099.6000506@marco.de> (raw)
In-Reply-To: <CABYL=To=tK8a0DVjvYeyuA2K4xChE3hv7Ppx+VvBTYfeZGgsjQ@mail.gmail.com>
Hello,
here is a screendump of a atop -dD in such a situation.
Regards
Daniel
Am 04/24/2012 05:00 PM, schrieb Roberto Spadim:
> it´s a read, a write, or both operation?
> about load i think it´s a very big read (sdb) with a very low write (sda)
> the disk balance on raid1 is based on nearest (current position - next
> read position) disk
> on a sequencial read only one disk is better used
>
> i checked that raid1 'have this problem' but it´s a hardware limit, i
> didn´t found a solution, maybe others friends can found
>
> Em 24 de abril de 2012 11:46, Daniel Spannbauer <ds@marco.de
> <mailto:ds@marco.de>> escreveu:
>
> Hello,
>
> at the moment I'm trying to find a bottleneck on my lamp-server with
> opensuse 11.4 (Kernel 2.6.37.6)
>
> Sometimes the system has a very poor performance because of a high
> io-wait.
> If I watch the systems disk-access with "atop -dD" I can see that sda is
> the most of the time at a load of 10%, sdb sometimes is at 100% or
> higher at the same time.
>
> In my opinion in a Raid1-System both disk should have nearly the
> same load.
>
> Or may I wrong whis this?
>
> Both harddisks where changed 3 Weeks ago, /proc/mdstat shows that the
> rebuild was successfull and the array is functional. Today I've changed
> th SATA-Cable and the Port on the Maindboard of sdb, but the behaviour
> is still the same. Both disks passed the extended smart-self-test.
>
> Any ideas about that?
>
> Regards
>
> Daniel
>
>
>
> --
> Daniel Spannbauer Software Entwicklung
> marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27
> <tel:%2B49%208333%209233-27> Fax -11
> Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220
> <tel:%2B49%20171%204033220>
> http://www.marco.de/ Email ds@marco.de
> <mailto:ds@marco.de>
> Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
> --
> Roberto Spadim
> Spadim Technology / SPAEmpresarial
--
Daniel Spannbauer Software Entwicklung
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds@marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
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:[~2012-04-24 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:46 Raid1: sdb has a lot mor work then sda Daniel Spannbauer
[not found] ` <CABYL=To=tK8a0DVjvYeyuA2K4xChE3hv7Ppx+VvBTYfeZGgsjQ@mail.gmail.com>
2012-04-24 15:02 ` Daniel Spannbauer [this message]
2012-04-24 15:04 ` Roberto Spadim
2012-04-24 15:03 ` Roberto Spadim
2012-04-25 7:47 ` Kay Diederichs
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=4F96C099.6000506@marco.de \
--to=ds@marco.de \
--cc=linux-raid@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).