Bug 1006698
Summary: | glfs_preadv_async fails for large read with io-cache xlator on | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Bharata B Rao <bharata.rao> |
Component: | io-cache | Assignee: | GlusterFS Bugs list <gluster-bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | aavati, bugs, gluster-bugs, ndevos, vbellur |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-27 18:32:37 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: |
Description
Bharata B Rao
2013-09-11 06:55:42 UTC
This could be a blocker for supporting gluster protocol in qemu-iotests. qemu-iotests is a test framework within QEMU to test the block layer in QEMU. We could permanently disable io-cache translator for the test gluster volume that gets created in qemu-iotests, but does GlusterFS recommend that ? Disabling io-cache is a reasonable workaround. io-cache is anyways designed for read-only workloads (while a VM image workload is read-write). So disabling io-cache should not have side too many effects. io-cache gets disabled in the 'virt' group file, see bug 851237 *** This bug has been marked as a duplicate of bug 851237 *** |