>>> [ ... ] reshape was running it was running around 4mb/s, >>> which is slow to begin with. [ ... resync too ... ] >> A bigger value for 'md/stripe-cache' might help, alleviating >> some alignment issues, but usually it is not like 10 times >> better, but might be still worthwhile even if it will be still >> slow. > I tried values up to 32768, but no difference. Then probably the partitions are really misaligned. Anyhow a wev search for similar cases shows in some cases higher reshape and resync rates, but not enormously higher, and usually 'stripe_cache' helps, at least with the reshape. Perhaps disabling barriet might help if they are enabled, but that would be quite dangerous, as you already had a crash during reshape. It may be good to reassemble the array with '--freeze-reshape' to allow it to resync without interference from reshaping, hopefully faster, and then '--continue' after resyning has ended. -- 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
