From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: responsiveness during raid check (Was: Problems with RAID 6 across 15 disks)
Date: Fri, 2 Apr 2010 07:55:08 +0200 [thread overview]
Message-ID: <20100402055508.GA15102@maude.comedia.it> (raw)
In-Reply-To: <20100402074325.3ce34e8f@notabene.brown>
On Fri, Apr 02, 2010 at 07:43:25AM +1100, Neil Brown wrote:
>On Thu, 01 Apr 2010 15:07:27 +0100
>Max Eaves <max@maxeaves.co.uk> wrote:
>
>> Doug,
>>
>> Thank you very much for that; a great relief off my shoulders.
>>
>> You are right - there is a config file located in
>> /etc/sysconfig/raid-check. I've changed ENABLED to no.
>
>However there is real value in doing that check, at least occasionally. It
>catches latent read errors.
>
>You might want to run it only every couple of months, and you might want to
>wind down one of both of the /proc/sys/dev/raid/speed_limit_* numbers so
>there is minimal impact on your system.
>
sorry if i am hijacking, but i got a report from one user that the
scheduled scrubbing is severely impacting responsiveness, lowering the
speed_limits seems to help a bit, but he reports it is still sluggish,
i always believed the check should use idle time, and not impact
performance that much. could it be scheduler related?
regards,
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
prev parent reply other threads:[~2010-04-02 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 13:23 Problems with RAID 6 across 15 disks Max Eaves
2010-04-01 13:49 ` Doug Ledford
2010-04-01 14:07 ` Max Eaves
2010-04-01 20:43 ` Neil Brown
2010-04-01 22:46 ` Piergiorgio Sartor
2010-04-01 22:58 ` Jools Wills
2010-04-01 23:04 ` Piergiorgio Sartor
2010-04-01 23:46 ` Michael Evans
2010-04-02 1:40 ` Jools Wills
2010-04-02 5:03 ` Neil Brown
2010-04-02 8:22 ` Piergiorgio Sartor
2010-04-02 10:21 ` Max Eaves
2010-04-02 5:55 ` Luca Berra [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=20100402055508.GA15102@maude.comedia.it \
--to=bluca@comedia.it \
--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