Bug 986812
Summary: | [performance/write-behind] errno always set to EIO eventhough the brick returns ENOSPC/EDQUOT | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | pushpesh sharma <psharma> |
Component: | glusterfs | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
Status: | CLOSED EOL | QA Contact: | amainkar |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | david.macdonald, ppai, rhs-bugs, rwheeler, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-03 17:18:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 985862 |
Description
pushpesh sharma
2013-07-22 07:25:20 UTC
> Expected results: > > 1. Is it a know limitation, never sighted a documentation. Might be I > overlooked,any reference can be provided.Else it should be documented as know > limitation. Yes it is. I think we should document this. > > 2. What should be error message in this case I/O error does not make much sense. The correct error in this case is ENOSPC (No space left on the device) and not EIO. That is the bug we should fix here. In the presence of write-behind translator, EIO is returned. On turning off write-behind, ENOSPC is returned as expected. This is most likely a bug in write-behind translator. Refer to the following code snippet from xlators/performance/write-behind/src/write-behind.c : wb_fulfill_cbk if (op_ret == -1) { wb_fulfill_err (head, op_errno); } else if (op_ret < head->total_size) { /* * We've encountered a short write, for whatever reason. * Set an EIO error for the next fop. This should be * valid for writev or flush (close). * * TODO: Retry the write so we can potentially capture * a real error condition (i.e., ENOSPC). */ wb_fulfill_err (head, EIO); } Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release. |