September 20, 20169 yr On my 6.2 double parity rig I had to replace a failing disk. The data rebuild took place and finished successfully. After the data rebuild the UI shows a successful parity check with that same date of the data rebuild. The data disk has not been read - just written. How can this be a successful parity check? IMHO, the UI is wrong here. A successful data rebuild has been processed, no parity check. Many thank in advance.
September 20, 20169 yr You're absolutely correct => this is an error. Not only is a rebuild NOT a parity check; but you SHOULD do a parity check after the rebuild to confirm all went well. Note that this is the ONE time I recommend doing a non-correcting check; so if anything did go awry, you can repeat the rebuild. Is this erroneous info also shown in the parity check "HIstory" ??
September 20, 20169 yr Author Yes, the history seems to be wrong as well: 2016 Sep 20 06:47:46|50906|117,9 MB/s|0 Regards
September 20, 20169 yr Author Found additional error reports in the announcement forum here: http://lime-technology.com/forum/index.php?topic=51874.msg499005#msg499005
September 20, 20169 yr And here, in middle paragraph. Not a rebuild but a clear after new drive added. I added a bit of detail from the syslog, as I can see why it gets confused.
September 20, 20169 yr While it's not good that these events are misreported as parity checks (hopefully they'll be resolved); remember that the first thing you should do after a rebuild is a parity check to confirm all went well => and as long as you do that, you'll indeed have a correctly annotated last check time
Archived
This topic is now archived and is closed to further replies.