oVirt manages only the FUSE mounts while the bricks are usually pushed in the /etc/fstab.<div>Of course when you use multiple layers like VDO + software raid (for example) + LVM , the simple fstab doesn't deal properly with it - so I just remove bricks from fstab and put them in systemd mount units.</div><div><br></div><div><div>[root@ovirt ~]# systemctl cat gluster_bricks-largedata.mount --no-pager</div><div># /etc/systemd/system/gluster_bricks-largedata.mount</div><div>[Unit]</div><div>Description=Mount glusterfs brick</div><div>Before = glusterd.service</div><div>Conflicts = umount.target</div><div><br></div><div>[Mount]</div><div>What=/dev/gluster_vg_largedata/largedata</div><div>Where=/gluster_bricks/largedata</div><div>Type=xfs</div><div>Options=noatime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0"</div><div><br></div><div>[Install]</div><div>WantedBy=glusterd.service</div><div><br></div><div><br></div> <div>You can use the options in /etc/fstab.</div><div><br></div><div><br></div>Keep in mind that the name of the mount unit has to match the physical location and any special characters have to be escaped.</div><div><br></div><div>For example if you mount your brick at /gluster/brick-1 your mount unit will be (don't forget to add '.mount' to the output of systemd-escape):</div><div><br></div><div>[root@ovirt ~]# systemd-escape -p /gluster/brick-1/</div><div>gluster-brick\x2d1</div><div>[root@ovirt ~]#</div><div><br></div><div><br></div><div>Best Regards,</div><div>Strahil Nikolov</div><div><br> <blockquote style="margin: 0 0 20px 0;"> <div style="font-family:Roboto, sans-serif; color:#6D00F6;"> <div>On Tue, Apr 5, 2022 at 16:47, Olaf Buitelaar</div><div><olaf.buitelaar@gmail.com> wrote:</div> </div> <div style="padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px solid #6D00F6;"> <div id="yiv8478330005"><div><div dir="ltr">Hi Strahil,<div><br clear="none"></div><div>interesting, would you happen to know how you could let oVirt mount it with this flag?</div><div><br clear="none"></div><div>Thanks Olaf</div></div><br clear="none"><div class="yiv8478330005gmail_quote"><div dir="ltr" class="yiv8478330005gmail_attr">Op ma 4 apr. 2022 om 22:05 schreef Strahil Nikolov <<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:hunter86_bg@yahoo.com" target="_blank" href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>>:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="yiv8478330005gmail_quote">* it instructs the kernel to skip 'getfattr'<br clear="none"> <br clear="none"> <blockquote style="margin:0px 0px 20px;"> <div style="font-family:Roboto, sans-serif;color:rgb(109,0,246);"> <div>On Mon, Apr 4, 2022 at 23:04, Strahil Nikolov</div><div><<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:hunter86_bg@yahoo.com" target="_blank" href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote:</div> </div> <div style="padding:10px 0px 0px 20px;margin:10px 0px 0px;border-left:1px solid rgb(109,0,246);"> <div id="yiv8478330005gmail-m_193295490234345777yiv7166561846"><div>I agree. Also it has a typo.Obviously I needed more coffee or a bigger break.<div><br clear="none"><div>It should be treated as 'relatime/noatime reduce the ammount of I/O requests to your brick physical device , which increases performance by reducing unnecessary IOPS'</div><div><br clear="none"></div><div>Same is valid for SELINUX's mount option:</div><div>context="system_u:object_r:glusterd_brick_t:s0" . It instructs the kernel to 'getfattr' each file in the brick as it has a specific selinux context (this case Gluster brick files), thus reducing unnecessary IOPS.</div><div><br clear="none"></div><div><br clear="none"></div><div><br clear="none"></div><div>Best Regards,</div><div>Strahil Nikolov<br clear="none"> <br clear="none"> <div id="yiv8478330005gmail-m_193295490234345777yiv7166561846yqt18695"><blockquote style="margin:0px 0px 20px;"> <div style="font-family:Roboto, sans-serif;color:rgb(109,0,246);"> <div>On Mon, Apr 4, 2022 at 9:41, Diego Zuccato</div><div><<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:diego.zuccato@unibo.it" target="_blank" href="mailto:diego.zuccato@unibo.it">diego.zuccato@unibo.it</a>> wrote:</div> </div> <div style="padding:10px 0px 0px 20px;margin:10px 0px 0px;border-left:1px solid rgb(109,0,246);"> Il 03/04/2022 16:36, Strahil Nikolov ha scritto:<br clear="none"><br clear="none">> Using relative/noatime mount option reduces the I/O to the brick device.IMVHO this sentence could cause misunderstandings. :)<br clear="none">It could be read like "noatime slows down your brick" while, IIUC, it <br clear="none">really means it *improves* the brick's performance by reducing the <br clear="none">number of "housekeeping" IOs.<br clear="none"><br clear="none">-- <br clear="none">Diego Zuccato<br clear="none">DIFA - Dip. di Fisica e Astronomia<br clear="none">Servizi Informatici<br clear="none">Alma Mater Studiorum - Università di Bologna<br clear="none">V.le Berti-Pichat 6/2 - 40127 Bologna - Italy<br clear="none">tel.: +39 051 20 95786<div id="yiv8478330005gmail-m_193295490234345777yiv7166561846yqtfd72375"><br clear="none">________<br clear="none"><br clear="none"><br clear="none"><br clear="none">Community Meeting Calendar:<br clear="none"><br clear="none">Schedule -<br clear="none">Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br clear="none">Bridge: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://meet.google.com/cpu-eiue-hvk">https://meet.google.com/cpu-eiue-hvk</a><br clear="none">Gluster-users mailing list<br clear="none"><a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:Gluster-users@gluster.org" target="_blank" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br clear="none"><a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a><div id="yiv8478330005yqtfd12951" class="yiv8478330005yqt3228016856"><br clear="none"></div></div><div id="yiv8478330005yqtfd25126" class="yiv8478330005yqt3228016856"> </div></div><div id="yiv8478330005yqtfd80456" class="yiv8478330005yqt3228016856"> </div></blockquote></div></div></div></div></div><div id="yiv8478330005yqtfd93439" class="yiv8478330005yqt3228016856"> </div></div><div id="yiv8478330005yqtfd75456" class="yiv8478330005yqt3228016856"> </div></blockquote><div id="yiv8478330005yqtfd10884" class="yiv8478330005yqt3228016856">________<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
Community Meeting Calendar:<br clear="none">
<br clear="none">
Schedule -<br clear="none">
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br clear="none">
Bridge: <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://meet.google.com/cpu-eiue-hvk">https://meet.google.com/cpu-eiue-hvk</a><br clear="none">
Gluster-users mailing list<br clear="none">
<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:Gluster-users@gluster.org" target="_blank" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br clear="none">
<a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br clear="none">
</div></blockquote></div><div id="yiv8478330005yqtfd13069" class="yiv8478330005yqt3228016856">
</div></div></div> </div> </blockquote></div>