Populates device block size before hidden sector #546
Merged
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
Now populates the block size (physical) before the hidden sector determination function runs. The naming of block/sector can be very confusing in nwipe. So I have created a device_phy_sector_size in the drive context, so we have ->device_sector_size // logical sector size ->device_phys_sector_size // physical sector size ->device_block_size // Usually the same as logical size but could be increased by nwipe to encompass multiple logical sectors, i.e a block of sectors
PartialVolume
deleted the
Determine_block_sizes_before_hidden_sector_detection
branch
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.
Now populates the block size (physical) before
the hidden sector determination function runs.
The naming of block/sector can be very confusing in nwipe. So I have created a device_phy_sector_size
in the drive context, so we have
->device_sector_size // logical sector size
->device_phys_sector_size // physical sector size
->device_block_size // Usually the same as logical size but could be increased by nwipe to encompass
multiple logical sectors, i.e a block of sectors