Setting To Ignore Parity For Initiator Mode Data Transfers #202
+32
−8
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
androda
force-pushed
the
InitiatorIgnoreParityErrors
branch
from
85dc3c4
to
6f4f792
Compare
erichelgeson
approved these changes
Oct 21, 2024
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.
Adding a new ini file option to ignore parity errors in initiator mode. Very old SCSI 1 drives, such as those using SCSI to Winchester adapters, might not support parity at all. This causes an incredibly slow data backup because a warning is written to the log for every block of data transferred.
This is how the INI file should be structured to disable initiator mode parity checking: