shard: correct file-size xattr in fallocate request failure #4523
Conversation
This file contains hidden or 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
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
When the fallocate request to a file returns a failure, there may actually be data written to the backend bricks. So, we do need to refresh file-size xattr for such a file, in that case. Fixes: gluster#4522 Signed-off-by: chenjinhao <[email protected]>
chen1195585098
force-pushed
the
fix_shards_remove_failure
branch
from
25e0f8f to
db73059
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When the fallocate request to a file returns a failure, there may actually be data written to the backend bricks. So, we do need to refresh file-size xattr for such a file, in that case.
Fixes: #4522