From: Neil Brown <neilb@suse.de>
To: "Rainer Shiz" <rainer.shiz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID Sync Speeds
Date: Tue, 23 May 2006 21:11:40 +1000 [thread overview]
Message-ID: <17522.60908.335242.982796@cse.unsw.edu.au> (raw)
In-Reply-To: message from Rainer Shiz on Tuesday May 23
On Tuesday May 23, rainer.shiz@gmail.com wrote:
> Thanks Neil and Chris for your quick replies.
>
> Neil, well when you say 'detectable activity' what do you exactly
> refer to.
It should mean any IO request to any of the physical devices, whether
though the raid array or otherwise. Sometimes in can get confused,
but in 2.6.12 (If it a kernel.org 2.6.12) got it pretty right I
think. Current kernels may have occasional issues that I really need
to sort out one day...
Maybe if you give me more precise details about your setup
(e.g. cat /proc/mdstat) something might occur to me.
> I heard that speed values are averaged out for about 5 minutes or so.
They are averaged over 30 seconds.
>
> One more question while I am at it, if a RAID Set is newly created and
> syncing, and now I change the /proc/sys/dev/raid/speed_limit_min and
> max values will this reflect on new RAID Sets that are created henceforth
> or even the existing RAID Sets which are being synced currently?
These numbers apply globally to all arrays, and can be changed at any
time.
More recent kernels have similar numbers in /sys/block/mdX/md/..
which allow the same settings to be applied to individual arrays.
>
> And yes, I am too using Seagate hard drives. Does mixing up of
> hard drives (vendors) affect this sync process.? (I presume not but please
> correct me if I am wrong).
Mixing things shouldn't have an unexpected effect. Obviously the
total speed will be limited by the slowest device, but no other
effects that I can thing of. Certainly not what you are experiencing.
NeilBrown
prev parent reply other threads:[~2006-05-23 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 13:05 Rainer Shiz
2006-05-22 17:02 ` Chris Boot
2006-05-22 22:42 ` Neil Brown
2006-05-23 7:37 ` Rainer Shiz
2006-05-23 11:11 ` Neil Brown [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=17522.60908.335242.982796@cse.unsw.edu.au \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rainer.shiz@gmail.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
all inboxes | Powered by JetHome®