There are two things you need to change for o-direct to be handled properly
in gluster stack:
1) gluster volume set performance.strict-o-direct on
on nfs this option is gluster volume set
performance.nfs.strict-o-direct on
2) gluster volume set network.remote-dio off
Please note that we found
By "mount -t glusterfs :/testvol -o direct-io-mode=true mountpoint",the
GlusterFS client will enable the direct io, and the file will not cached in the
GlusterFS client,but it won't work in the GlusterFS server. By defalut,the
GlusterFS will ignore the direct io flag. How to make the server
t;Raghavendra Gowdappa" wrote:
>
>
>- Original Message -
>> From: "Keiviw"
>> To: gluster-devel@gluster.org
>> Sent: Tuesday, March 22, 2016 1:18:18 PM
>> Subject: [Gluster-devel] How to enable DIRECT IO?
>>
>> hi,
>> In the
- Original Message -
> From: "Keiviw"
> To: gluster-devel@gluster.org
> Sent: Tuesday, March 22, 2016 1:18:18 PM
> Subject: [Gluster-devel] How to enable DIRECT IO?
>
> hi,
> In the glusterfs client, execute "mount -t glusterfs volumename -o
> di
hi,
In the glusterfs client, execute "mount -t glusterfs volumename -o
direct-io-mode=enable mountpoint".
Does it mean that the client reads or writes the cluster files in the way of
DIRECT IO? If not,how to enable DIRECT IO?___
Gluster-devel mailing li
