Core: Survive random remove/add uevent pairs on blocks #61
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
These event pairs usually happen asynchronously sometime after creating a partition, when udev issues a BLKRRPART as part of synthesizing a change event for the parent device. This tries to fix the same issue as eb4b994, which doesn't seem to be effective. Unfortunately, the fix only helps with the storaged internals; it is still possible that external programs such as wipefs will find the block device missing when they happen to look for it after the remove and before the add.
|
Hold on! I have a better idea! (flock) |
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.
These event pairs usually happen asynchronously sometime after
creating a partition, when udev issues a BLKRRPART as part of
synthesizing a change event for the parent device after there was
already a add event for the new partition.
This tries to fix the same issue as eb4b994, which doesn't seem to be
effective.