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 <[EMAIL PROTECTED]>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
