Bug 1552070
| Summary: | Unable to set VDO writepolicy to auto | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, dkota, rcyriac, rhinduja, rhs-bugs, rreddy, sabose, sasundar, smohan, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.3.1 Async | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.2-25 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1552063 | Environment: | |
| Last Closed: | 2018-06-21 03:33:15 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: | 1552063, 1581561 | ||
|
Description
SATHEESARAN
2018-03-06 12:39:32 UTC
sas, which version of VDO are you using?
As per vdo documentation they allow only sync and async.
============
--writePolicy={ sync | async }
Specifies the write policy:
sync Writes are acknowledged only after data is stably written. This is the default policy. This policy
is not supported if the underlying storage is not also synchronous.
async Writes are acknowledged after data has been cached for writing to stable storage. Data which has not
been flushed is not guaranteed to persist in this mode.
========
[root@localhost ~]# rpm -qa | grep vdo
kmod-kvdo-6.1.0.55-9.el7.x86_64
vdo-6.1.0.55-10.x86_64
The latest VDO supports the writePolicy 'auto'
vdo versions are below:
kmod-kvdo-6.1.0.153-15.el7.x86_64
vdo-6.1.0.149-16.x86_64
<snip_from_man_vdo>
--writePolicy={ sync | async | auto }
Specifies the write policy:
sync Writes are acknowledged only after data is stably written. This policy is not supported if the underlying storage is not also synchronous.
async Writes are acknowledged after data has been cached for writing to stable storage. Data which has not been flushed is not guaranteed to persist in this mode.
auto VDO will check the storage device and determine whether it supports flushes. If it does, VDO will run in async mode, otherwise it will run in sync mode. This is the default.
</snip_from_man_vdo>
sas, this bug should be fixed in Ansible 2.5. This is a bug in the vdo ansible module itself. Which is part of Ansible now. We are removing the ansible module from gdeploy. Which is addressed here: https://github.com/gluster/gdeploy/pull/495/commits/38e5c041fd64df4 And Devyani will be adding Ansible 2.5 as the dependency in the next build. Tested with gdeploy-2.0.2-26.el7rhgs. writePolicy now could be set to 'auto' Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1958 |