hack: add blanket retries on device-mapper failures with SCSI #1720
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
After moving to 5.10+ we started seeing occasional failures when creating verity/crypt device-mapper targets. Longer term fix should be adding retries on particular errors at lower level e.g. in devicemapper/crypt packages. Signed-off-by: Maksim An <maksiman@microsoft.com>
helsaawy
approved these changes
Apr 7, 2023
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.
After moving to 5.10+ we started seeing occasional failures when creating verity/crypt device-mapper targets.
Longer term fix should be adding retries on particular errors at lower level e.g. in devicemapper/crypt packages.
The other PR is currently in draft: #1721