Handle write-perm on LOCATE correctly #233
Merged
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.
Summary of changes
Override the error code to
LTFS_LOCATE_ERROR
when tape backend'slocate()
call returns write-perm error.Description
On #232, LTFS could remove files automatically when tape backend's
locate()
call returns write-perm error even if It is not necessary. But I believe this is so rare like breaking H/W.Fixes #232
Type of change
Checklist: