[Gluster-users] Indexing/Importing existing files on disk

[Strahil Nikolov]

oVirt manages only the FUSE mounts while the bricks are usually pushed in the /etc/fstab.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.
[root at ovirt ~]# systemctl cat gluster_bricks-largedata.mount --no-pager# /etc/systemd/system/gluster_bricks-largedata.mount[Unit]Description=Mount glusterfs brickBefore = glusterd.serviceConflicts = umount.target
[Mount]What=/dev/gluster_vg_largedata/largedataWhere=/gluster_bricks/largedataType=xfsOptions=noatime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0"
[Install]WantedBy=glusterd.service

 You can use the options in /etc/fstab.

Keep in mind that the name of the mount unit has to match the physical location and any special characters have to be escaped.
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):
[root at ovirt ~]# systemd-escape -p /gluster/brick-1/gluster-brick\x2d1[root at ovirt ~]#

Best Regards,Strahil Nikolov
 
  On Tue, Apr 5, 2022 at 16:47, Olaf Buitelaar<olaf.buitelaar at gmail.com> wrote:   Hi Strahil,
interesting, would you happen to know how you could let oVirt mount it with this flag?
Thanks Olaf
Op ma 4 apr. 2022 om 22:05 schreef Strahil Nikolov <hunter86_bg at yahoo.com>:

* it instructs the kernel to skip 'getfattr'
 
 
  On Mon, Apr 4, 2022 at 23:04, Strahil Nikolov<hunter86_bg at yahoo.com> wrote:   I agree. Also it has a typo.Obviously I needed more coffee or a bigger break.
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'
Same is valid for SELINUX's mount option: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.


Best Regards,Strahil Nikolov
 
 
  On Mon, Apr 4, 2022 at 9:41, Diego Zuccato<diego.zuccato at unibo.it> wrote:   Il 03/04/2022 16:36, Strahil Nikolov ha scritto:

> Using relative/noatime mount option reduces the I/O to the brick device.IMVHO this sentence could cause misunderstandings. :)
It could be read like "noatime slows down your brick" while, IIUC, it 
really means it *improves* the brick's performance by reducing the 
number of "housekeeping" IOs.

-- 
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users at gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
  
  
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users at gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20220405/cfaafcda/attachment.html>