- Minor
I have had this problem for at least 3 stable releases, upgrading each time in hope it can be fixed.
As of right now, I have a massive move operation going on, and it reaches 50 Megabytes per second max going from cache to array.
I know it can do better because a parity check can go upwards of 100 Megabytes per second on the same array.
What the *BLEEP* can I do to fix this. It has become very annoying!