From: Bill Davidsen <davidsen@tmr.com>
To: Niccolo Rigacci <niccolo@rigacci.org>
Cc: linux-raid@vger.kernel.org, Mark Hahn <hahn@physics.mcmaster.ca>
Subject: Re: New FAQ entry? (was IBM xSeries stop responding during RAID1 reconstruction)
Date: Thu, 22 Jun 2006 23:14:51 -0400 [thread overview]
Message-ID: <449B5CAB.50409@tmr.com> (raw)
In-Reply-To: <20060622071145.GA718@rigacci.org>
Niccolo Rigacci wrote:
>>>personally, I don't see any point to worrying about the default,
>>>compile-time or boot time:
>>>
>>>for f in `find /sys/block/* -name scheduler`; do echo cfq > $f; done
>>>
>>>
>
>I tested this case:
>
>- reboot as per power failure (RAID goes dirty)
>- RAID start resyncing as soon as the kernel assemble it
>- every disk activity is blocked, even DHCP failed!
>- host services are unavailable
>
>This is why I changed the kernel default.
>
>
>
Changing on the command line assumes that you built all of the
schedulers in... but making that assumption, perhaps the correct
fail-safe is to have cfq as the default, and at the end of rc.local
check for rebuild, and if everything is clean change to whatever work
best at the end of the boot. If the raid is not clean stay with cfq.
Has anyone tried deadline for this? I think I had this as deafult and
didn't hand on a raid5 fail/rebuild.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-06-23 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 16:09 New FAQ entry? (was IBM xSeries stop responding during RAID1 reconstruction) Niccolo Rigacci
2006-06-21 17:10 ` David Greaves
2006-06-21 18:51 ` Michael Tokarev
2006-06-22 2:20 ` Mark Hahn
2006-06-22 4:35 ` Gil
2006-06-22 7:11 ` Niccolo Rigacci
2006-06-23 3:14 ` 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=449B5CAB.50409@tmr.com \
--to=davidsen@tmr.com \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-raid@vger.kernel.org \
--cc=niccolo@rigacci.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).