quoted
2007/12/27, Cody Yellan [off-list ref]:
quoted
I had a 4x500GB SATA2 array, md0. I added one 500GB drive and
reshaping began at ~2500K/sec. Changing
/proc/sys/dev/raid/speed_limit_m{in,ax} or
/sys/block/md0/md/sync_speed_m{in,ax} had no effect. I shut down
all
quoted
quoted
unnecessary services and the array is offline (not mounted). I
have
quoted
quoted
read that the throttling code is "fragile" (esp. with regard to
raid5) but does this make sense? I will wait (in)patiently for it
to
quoted
quoted
finish, but I do wonder why the configuration parameters have no
effect. This is a dual quad 2GHz Xeon machine with 8GB of memory
running RHEL5. Is this the maximum speed?
I think you may check each SATA2 disk to make sure they are working
fine.
quoted
I had a similar situation and it turned out to be caused by one of
disks in array. It is a failed disk indicated by its S.M.A.R.T
information.
No problems indicated by SMART but I did have some concerns about the
drive I added. It contained some data so I tried to delete the
partition and create a new filesystem-free partition. Both parted
and fdisk simply restored the already existing partition, complete
with the data. So I just added that drive, figuring mdadm would
overwrite the partition. It worked but from now on I will try to
use only blank disks.