10:05 a.m.
Hello everyone. I have a Gluster distributed replication cluster deployed. The cluster -
store for ovirt. For bricks - VDO over a raw disk. When discarding via 'fstrim
-av' the storage hangs for a few seconds and the connection is lost. Does anyone know
the best practices for using TRIM with VDO in the context of ovirt?
ovirt - v4.4.10
gluster - v8.6
1:35 a.m.
This is quite odd. Is your raw disks responsive during the fstrim ?What happens if you
trigger it more often ?
What disks do you use ?
Best Regards,Strahil Nikolov
On Tue, Mar 29, 2022 at 10:06, Oleh Horbachov<gorbyo(a)gmail.com> wrote: Hello
everyone. I have a Gluster distributed replication cluster deployed. The cluster - store
for ovirt. For bricks - VDO over a raw disk. When discarding via 'fstrim -av' the
storage hangs for a few seconds and the connection is lost. Does anyone know the best
practices for using TRIM with VDO in the context of ovirt?
ovirt - v4.4.10
gluster - v8.6
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UCTN2ZIG3ED...
10:45 a.m.
Hello. The issue is at same time difficult and easy to reproduce.
Easy because I can reproduce 1 time from 3-4 run
Difficult because I cant to catch start and stop the issue
Answers to your questions
1. In general disks responsive during the fstrim
2. I run trigger every week but ih different day of week for each storage
3. I use nvme disks.
I tried to do reproduce the issue manually and found following
1. Affected only for one host of storage cluster (i think because main mount point)
2. In ovirt events found
"Host ovirt-host-03 cannot access the Storage Domain(s) glusterfs-data attached to
the Data Center Computing. Setting Host state to Non-Operational." and after that
event oVirt started migration from host-03
I think the issue is VDSM
In additional found at host ovirt-host-03 in vdsm.log few errors at time during fstrim
like
"ERROR (monitor/2ac7658) [storage.Monitor] Error checking domain
2ac76580-2182-470d-b886-d3d2e28d05b3 (monitor:453)"
2ac... - uuid gluster domain
I have 6 hosts in cluster with same install and affected only one
10:47 a.m.
I have 6 hosts in oVirt cluster with same install and affected only one
Best regards,
Oleh Horbachov
958
days inactive
968
days old
3 comments
2 participants
participants (2)
-
Oleh Horbachov -
Strahil Nikolov