From: Bill Davidsen <davidsen@tmr.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Gabor Gombas <gombasg@sztaki.hu>,
linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Re: IBM xSeries stop responding during RAID1 reconstruction
Date: Mon, 26 Jun 2006 10:52:52 -0400 [thread overview]
Message-ID: <449FF4C4.2050700@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606200757300.30567@filesrv1.baby-dragons.com>
Mr. James W. Laferriere wrote:
> Hello Gabor ,
>
> On Tue, 20 Jun 2006, Gabor Gombas wrote:
>
>> On Tue, Jun 20, 2006 at 03:08:59PM +0200, Niccolo Rigacci wrote:
>>
>>> Do you know if it is possible to switch the scheduler at runtime?
>>
>> echo cfq > /sys/block/<disk>/queue/scheduler
>
>
> At least one can do a ls of the /sys/block area & then do an
> automated
> echo cfq down the tree . Does anyone know of a method to set a
> default
> scheduler ? Scanning down a list or manually maintaining a list
> seems
> to be a bug in the waiting . Tia , JimL
Thought I posted this... it can be set in kernel build or on the bloot
parameters from grub/lilo.
2nd thought: set it to cfq by default, then at the END of rc.local, if
there are no arrays rebuilding, change to something else if you like.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-06-26 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 8:53 IBM xSeries stop responding during RAID1 reconstruction Niccolo Rigacci
2006-06-14 15:46 ` Bill Cizek
2006-06-15 9:12 ` Niccolo Rigacci
2006-06-15 10:13 ` Neil Brown
2006-06-17 10:01 ` Niccolo Rigacci
2006-06-19 15:05 ` Gabor Gombas
2006-06-20 13:08 ` Niccolo Rigacci
2006-06-20 13:27 ` Gabor Gombas
2006-06-20 15:00 ` Mr. James W. Laferriere
2006-06-20 15:45 ` Niccolo Rigacci
2006-06-20 16:38 ` Gabor Gombas
2006-06-26 14:52 ` Bill Davidsen [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=449FF4C4.2050700@tmr.com \
--to=davidsen@tmr.com \
--cc=babydr@baby-dragons.com \
--cc=gombasg@sztaki.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.