Repository navigation
Show what was skipped, and probe wide enough to see sparse damage - #6
Merged
Merged
Conversation
The dashboard's OVER column becomes SKIP: how much --skip-slow has condemned without reading, which the weak count cannot show since a region never read has no sectors to count. --status shows the same; chunks over budget stay in --status-json and the report. REGRESSION guarded: the probes that step a gigabyte forward read eight chunks, and damage in one chunk of twenty-five slipped past most of them, so a real drive with 4% of its chunks bad was called clean a gigabyte on and nothing was ever skipped. They read 64 MiB now; the bisection narrows to 8 MiB probes once the gap is smaller than a wide one, so a dense region's edge stays sharp. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The dashboard's OVER column becomes SKIP: how much --skip-slow has condemned without reading, which the weak count cannot show since a region never read has no sectors to count. --status shows the same; chunks over budget stay in --status-json and the report.
REGRESSION guarded: the probes that step a gigabyte forward read eight chunks, and damage in one chunk of twenty-five slipped past most of them, so a real drive with 4% of its chunks bad was called clean a gigabyte on and nothing was ever skipped. They read 64 MiB now; the bisection narrows to 8 MiB probes once the gap is smaller than a wide one, so a dense region's edge stays sharp.