You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we call faultTracker.CheckProvable before declaring a sector recovered. However, this will pass as long as the sector is on-disk and is the correct size, even if it's actually corrupted.
Unfortunately, this means that, for corrupted sectors that still exist, we'll:
Declare them "recovering".
Try to prove them.
Fail, skip them, and retry the proof.
Unfortunately, at step 3, we only re-try 5 times at the moment (fixed in #4633). This is usually sufficient, but not when there are many corrupted sectors.
We don't usually checksum sectors before attempting to prove them because this would force us to read every sector from disk (proving a sector only requires reading part of it). However, in this case, we know that the sector is more likely faulty than not so we should perform a more expensive check.
The text was updated successfully, but these errors were encountered:
Stebalien
changed the title
Additional checks required before invoking checkNextRecoveries
Additional checks required when recovering sectors in checkNextRecoveries
Oct 29, 2020
Currently, we call
faultTracker.CheckProvable
before declaring a sector recovered. However, this will pass as long as the sector is on-disk and is the correct size, even if it's actually corrupted.Unfortunately, this means that, for corrupted sectors that still exist, we'll:
Unfortunately, at step 3, we only re-try 5 times at the moment (fixed in #4633). This is usually sufficient, but not when there are many corrupted sectors.
We don't usually checksum sectors before attempting to prove them because this would force us to read every sector from disk (proving a sector only requires reading part of it). However, in this case, we know that the sector is more likely faulty than not so we should perform a more expensive check.
The text was updated successfully, but these errors were encountered: