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
-
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
Thanks to the several guys in this list, I have solved my problem
and elaborated this, can be a new FAQ entry?
Q: Sometimes when a RAID volume is resyncing, the system seems to
locks-up: every disk activity is blocked until resync is done.
A: This is not strictly related to Linux RAID, this
Niccolo Rigacci wrote:
[]
From the command line you can see which schedulers are supported
and change it on the fly (remember to do it for each RAID disk):
# cat /sys/block/hda/queue/scheduler
noop [anticipatory] deadline cfq
# echo cfq /sys/block/hda/queue/scheduler
Otherwise
There's much easier/simpler way to set default scheduler. As
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
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
Mark Hahn wrote:
There's much easier/simpler way to set default scheduler. As
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 agree -- if you're talking about changing the io