Test multiple blocks at once using badblocks when invoked by e2fsck #15
Conversation
This file contains 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
…d at once through to badblocks
|
Seems like a good feature. Can we get this added? On my 8TB drive, it takes about a week to finish the non-destructive read-write test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When
e2fsckis run with the-coption to usebadblocksto find any bad blocks on the device, it does so without specifying the number of blocks to test at once. This can cause a lot of seeks on mechanical hard drives and makes testing large drives incredibly slow.This pull request adds an option
-Kto thee2fsckcommand to allow the number of blocks tested at once bybadblocksto be specified when it is called bye2fsck -c.