NeilBrown wrote:
~$ grep . /sys/block/md2/md/*
...
/sys/block/md2/md/sync_speed:0
/sys/block/md2/md/sync_speed_max:0 (system)
/sys/block/md2/md/sync_speed_min:0 (system)
This looks like the culprit. The sync_speed has been limited to
0. The "(system)" means that it is using the value from
/proc/sys/dev/raid/speed_limit_max
It seem that that value has been set to 0 somehow.
The default value is 200000.
Could something be setting that? Can you set it back?
.../speed_limit_min should be 1000 by default.
NeilBrown
I'll set it back next time it happens. Any guess what might set that
value to 0 and why? mdadm is the only thing I know of that knows about
raid. It starts up late in the init process with this command:
/sbin/mdadm --monitor --pid-file /var/run/mdadm/monitor.pid --daemonise
--scan --syslog
Thanks for your help.
Randall
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html