+++ This bug was initially created as a clone of Bug #1312198 +++ Description of problem: 'gluster volume set <VOL> o-direct on' fails with the error 'this option does not exist'. We need to expose this option via the CLI. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Vijay Bellur on 2016-02-26 02:29:34 EST --- REVIEW: http://review.gluster.org/13529 (mgmt/glusterd: Expose storage.o-direct via CLI) posted (#1) for review on master by Krutika Dhananjay (kdhananj) --- Additional comment from Vijay Bellur on 2016-02-26 05:05:14 EST --- REVIEW: http://review.gluster.org/13529 (glusterd,posix: Expose storage.o-direct via CLI) posted (#2) for review on master by Krutika Dhananjay (kdhananj) --- Additional comment from Vijay Bellur on 2016-02-29 00:21:05 EST --- REVIEW: http://review.gluster.org/13529 (glusterd,posix: Expose storage.o-direct via CLI) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: http://review.gluster.org/13543 (glusterd,posix: Expose storage.o-direct via CLI) posted (#1) for review on release-3.7 by Krutika Dhananjay (kdhananj)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Closing this bug with WONTFIX as the reason since enabling o-direct just at posix layer can cause write failures with EINVAL due to offset and size alignment issues on O_DIRECT writes and therefore it is generally a bad practice.