Re: Triple parity and beyond

On 24-11-13 22:13, Stan Hoeppner wrote:

I freely admit I may have drawn an incorrect conclusion about md 
parity rebuild performance based on incomplete data. I simply don't 
recall anyone stating here in ~3 years that their parity rebuilds were 
speedy, but quite the opposite. I guess it's possible that each one of 
those cases was due to another factor, such as user load, slow CPU, 
bus bottleneck, wonky disk firmware, backplane issues, etc. 

The other part to this is, that the list sees what goes wrong. The cases 
where a replacement goes smoothly do not reach the list

Cheers,


Rudy