This repository has been archived by the owner on Dec 18, 2020. It is now read-only.
Reply to initiator with LUN busy when there is a read/write error from backend #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
…m backend Signed-off-by: Payes <payes.anand@cloudbyte.com>
Signed-off-by: Payes <payes.anand@cloudbyte.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If a check condition is returned with medium error, the iscsi initiator marks the volume as read only.
Errors with no space left on disk will be addressed later.
Manual testing was performed by attaching the volume to applications running on kubernetes pods.
After these fixes the Read Only state is avoided if there are network fluctuations or the replica is down for short period of time.
Signed-off-by: Payes payes.anand@cloudbyte.com