[SOLVED] Parity Check way slower with RC2 than RC1.

250MB/s average speed is impossible with the currently assigned array devices, it's most likely the result of an 8TB rebuild and an old bug, speed shown considers the full parity size vs the actual size rebuilt.

Then, are the 100MB/s and duration realistic speed for parity check with my disks or is the speed too slow?

 

100MB/S is realistic depending on the type of drives your are using.

 

One other factor that can screw the displayed speed of the check is pausing the check. I think it only considers the time after the check was resumed but still the complete capacity.

It looks like that's what happen to you from the picture.

 

Here is an example from my history:

When the parity check is paused midway, it will show the duration and speed calculation from the point it is resumed.

This results in an incorrect number, which is the case here.

 

My parity-check log shows rc2 achieves the same speed as earlier versions (including rc1).

 

Changed Status to Closed

Changed Priority to Other

Next Unraid version will have the correct values when parity check is paused and resumed.

1 hour ago, bonienl said:

Next Unraid version will have the correct values when parity check is paused and resumed.

Just for interest will this be for the whole run or just the last increment?  Just asking to see if I might need to revisit the code in the Parity Check Tuning plugin that tries to give the correct values for the run as a whole.

The GUI keeps track of pause and resume times, it uses these together with the existing vars to calculate the correct duration and speed.

 

This won’t affect your plugin.

 

2 hours ago, bonienl said:

Next Unraid version will have the correct values when parity check is paused and resumed.

Cool, would it be possible to also fix this long standing bug?

https://forums.unraid.net/bug-reports/stable-releases/clearrebuild-operations-are-reported-as-the-last-parity-check-and-with-the-wrong-avg-speed-if-drive-is-smaller-than-parity-r3/?do=getNewComment&d=2&id=3

First bug report created on this subforum

1 hour ago, JorgeB said:

would it be possible to also fix this long standing bug?

 

You have the memory of an elephant

Seems simple, but isn't straightforward to solve. I put it on my todo list!