From: John Wang <jwang@dataseekonline.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 resync speed problems
Date: Tue, 03 Jul 2007 10:58:08 -0500 [thread overview]
Message-ID: <C2AFDC40.38AE%jwang@dataseekonline.com> (raw)
In-Reply-To: <89f9efee0706131328r6db8c366u45f159de6d2aa9c9@mail.gmail.com>
Hello
Those WD RE drives are intended for use with TLER aware RAID controllers and
should not be directly attached to a server through a regular controller as
individual drives.
The reason is that TLER (Time Limited Error Recovery) will occasionally not
bother to recover data if it takes longer than a set period of time to do
so, this does not bother a TLER aware controller since it would just rebuild
the data from parity and would know enough that it's not really a failed
drive unless the issue keeps reoccurring in the same spot. If you use
these drives as regular drives, they could report more errors than a non RE
drive which is probably why you're getting the resyncs. The difference
between the two systems could simply be the number of bordeline flaws on the
drive which would normally be recovered by the drive itself but is being
passed on up to the OS as the drive assumes the RAID controller could make
better decisions as to what to do.
You may want to get yourself a Promise RAID controller as they are
considered TLER aware although their approach is quite simple i.e.: retry
several times before assuming it's a hard error (might as well not have TLER
with that approach). Better yet, get non-RE drives...
Regards,
John
On 6/13/07 3:28 PM, "Leonard Smith" <lrsmith@gmail.com> wrote:
> Forgot to mention, the drives are WD 500 GB "Raid enabled" SATA
> drives. They are some of WD newer drives, and I think they are
> techincally SATA2. The other system also has the same drives.
>
>
> On 6/13/07, Matthew Gillen <me@mattgillen.net> wrote:
>> Leonard Smith wrote:
>>> I am running CentOS4.4 on two "black" box systems that are
>>> identically configured. Both have 500 GB internal drives, ( same type)
>>> and were installed using the same kickstart configuration. The drives
>>> are being mirrored using LVM.
>>>
>>> When I check the first system it is re-syncing and the resync time and
>>> speed are
>>>
>>> finish=18559.6min speed=355K/sec
>>>
>>> On the second system the time and speed are
>>>
>>> finish=89.5min speed=68170K/sec
>>>
>>> I can't figure out why the speeds are different between the two. I
>>> checked /proc/sys/dev/raid/speed_limit_ and they are the same. The
>>> priority of the md proceses are they same.
>>>
>>> I tweaked the setting of the speel_limit_min and increase the nice
>>> priority of the resync process, on the first box, but I could never
>>> get it better than
>>>
>>> finish=4551.8min speed=1445K/sec
>>>
>>>
>>> I've googled and I haven't found much more useful information that to
>>> adjust those settings. Besides those setting what else dictates the
>>> speed used?
>>
>> You might compare the hd settings using 'hdparm'. I'm not sure factor of
>> 100+
>> can be explained by an incorrect DMA setting or something like that, but it
>> might be a contributor.
>>
>> Matt
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2007-07-03 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 1:52 [linux-lvm] LVM2 resync speed problems Leonard Smith
2007-06-13 19:05 ` Leonard Smith
2007-06-13 19:11 ` Matthew Gillen
2007-06-13 20:28 ` Leonard Smith
2007-07-03 15:58 ` John Wang [this message]
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=C2AFDC40.38AE%jwang@dataseekonline.com \
--to=jwang@dataseekonline.com \
--cc=linux-lvm@redhat.com \
/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).