Not sure I like this, for many spinning disk raids of that scale I have are mostly read, rarely write. With raid 6 for example, I pop in a new drive, and all t

Not sure I like this, for many spinning disk raids of that scale I have are mostly read, rarely write. With raid 6 for example, I pop in a new drive, and all the write/repair hits only that drive. With a virtual spare, all drives end up with massive writes, meaning I might hit write errors, thus borking a raid which would have been ok for reads. I realise there are 100 'what ifs' and scenarios here, but when my raids tend to drop a drive, it's on heavy write ops, not reads. I'd say 90% of the time. I imagine ssd cascading/eol write failures might make this virtual spare failure scenario even more likely. (yes I am aware of sector reallocation delays on spinning disks, I am referring to real EOL scenarios on drives during writes, being far more common for me than reads)