- Users - oVirt List Archives

Re: NFS Storage Domain on OpenMediaVault
by Amit Bawer 03 Dec '19

03 Dec '19

On Mon, Dec 2, 2019 at 7:21 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > Thanks for the response. > > As it turned out, the issue was on the export where I had to remove > subtree_check and added no_root_squash and it started working. > > Being new to the setup, I am still trying to work through some config > issues and deciding if I want to continue. The main thing I am looking for > is good HA and failover capability. Been using Proxmox VE and I like the > admin of it, but failover still needs work. Simple things like auto > migration when rebooting a host does not exist and is something I need. > for RHEV, you can check the Cluster scheduling policies https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… > Robert > ------------------------------ > *From:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Sent:* Sunday, December 1, 2019 2:54 PM > *To:* users(a)ovirt.org <users(a)ovirt.org>; Robert Webb <rwebb(a)ropeguru.com> > *Subject:* Re: [ovirt-users] NFS Storage Domain on OpenMediaVault > > Does sanlock user has rights on the ...../dom_md/ids ? > > Check the sanlock.service for issues. > journalctl -u sanlock.service > > Best Regards, > Strahil Nikolov > > В неделя, 1 декември 2019 г., 17:22:21 ч. Гринуич+2, rwebb(a)ropeguru.com < > rwebb(a)ropeguru.com> написа: > > > I have a clean install with openmediavault as backend NFS and cannot get > it to work. Keep getting permission errors even though I created a vdsm > user and kvm group; and they are the owners of the directory on OMV with > full permissions. > > The directory gets created on the NFS side for the host, but then get the > permission error and is removed form the host but the directory structure > is left on the NFS server. > > Logs: > > From the engine: > > Error while executing action New NFS Storage Domain: Unexpected exception > > From the oVirt node log: > > 2019-11-29 10:03:02 136998 [30025]: open error -13 EACCES: no permission > to open /rhev/data-center/mnt/192.168.1.56: > _export_Datastore-oVirt/f38b19e4-8060-4467-860b-09cf606ccc15/dom_md/ids > 2019-11-29 10:03:02 136998 [30025]: check that daemon user sanlock 179 > group sanlock 179 has access to disk or file. > > File system on Openmediavault: > > drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 . > drwxr-xr-x 9 root root 4096 Nov 27 20:56 .. > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 > f38b19e4-8060-4467-860b-09cf606ccc15 > > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 . > drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 .. > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 dom_md > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 images > > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 . > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 .. > -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 ids > -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 inbox > -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 leases > -rw-rw-r--+ 1 vdsm kvm 343 Nov 29 10:03 metadata > -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 outbox > -rw-rw----+ 1 vdsm kvm 1302528 Nov 29 10:03 xleases > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/ILKNT57F6VUHE… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/KH2H2V254Z7T7… >

2 1

NFS Storage Domain on OpenMediaVault
by rwebb＠ropeguru.com 02 Dec '19

02 Dec '19

I have a clean install with openmediavault as backend NFS and cannot get it to work. Keep getting permission errors even though I created a vdsm user and kvm group; and they are the owners of the directory on OMV with full permissions. The directory gets created on the NFS side for the host, but then get the permission error and is removed form the host but the directory structure is left on the NFS server. Logs: From the engine: Error while executing action New NFS Storage Domain: Unexpected exception From the oVirt node log: 2019-11-29 10:03:02 136998 [30025]: open error -13 EACCES: no permission to open /rhev/data-center/mnt/192.168.1.56:_export_Datastore-oVirt/f38b19e4-8060-4467-860b-09cf606ccc15/dom_md/ids 2019-11-29 10:03:02 136998 [30025]: check that daemon user sanlock 179 group sanlock 179 has access to disk or file. File system on Openmediavault: drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 . drwxr-xr-x 9 root root 4096 Nov 27 20:56 .. drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 f38b19e4-8060-4467-860b-09cf606ccc15 drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 . drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 .. drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 dom_md drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 images drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 . drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 .. -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 ids -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 inbox -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 leases -rw-rw-r--+ 1 vdsm kvm 343 Nov 29 10:03 metadata -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 outbox -rw-rw----+ 1 vdsm kvm 1302528 Nov 29 10:03 xleases

4 3

host failed to attach one of the storage domains attached to it
by Daniel Menzel 02 Dec '19

02 Dec '19

Dear all, after a GlusterFS reboot of two servers out of three (and thus a loss of quorum) by an admin we've got strange problems: 1. The hosted engine and one export work perfectly fine. (Same three servers!) 2. Another export (main one) seems to be fine within GlusterFS itself. But: When we activate this domain most of the hosts go into "non operational" with the subject's error message. As soon as we deactivate this domain all those hosts come back online. Strange thing: The GlusterFS export seems to be mounted on the SPM. Does anyone know what could have happened and how to fix that? Kind regards Daniel

1 0

Overt Networking VM not pinging
by Vijay Sachdeva 02 Dec '19

02 Dec '19

Dear Community, I have installed Ovirt Engine 4.3 and Ovirt Node 4.3. Node got successfully added to engine and setup host network also done. When trying to ping host using “ovirtmgmt” as vNic profile for a VM, it is not even able to ping it’s host or any other machine on that same network. Also added a VLAN network which is passed via same uplink of Node interface where “Ovirtmgmt” is passed, that is also not working. Although this vnet is vnic type is VirtIO and state shows “UNKNOWN”, would this be a problem? Any help would be highly appreciated. Thanks Vijay Sachdeva Senior Manager – Service Delivery IndiQus Technologies O +91 11 4055 1411 | M +91 8826699409 www.indiqus.com

3 7

hyperconverged single node with SSD cache fails gluster creation
by thomas＠hoberg.net 01 Dec '19

01 Dec '19

I am seeing more success than failures at creating single and triple node hyperconverged setups after some weeks of experimentation so I am branching out to additional features: In this case the ability to use SSDs as cache media for hard disks. I tried first with a single node that combined caching and compression and that fails during the creation of LVMs. I tried again without the VDO compression, but actually the results where identical whilst VDO compression but without the LV cache worked ok. I tried various combinations, using less space etc., but the results are always the same and unfortunately rather cryptic (substituted the physical disk label with {disklabel}): TASK [gluster.infra/roles/backend_setup : Extend volume group] ***************** failed: [{hostname}] (item={u'vgname': u'gluster_vg_{disklabel}p1', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_{disklabel}p1', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachedisk': u'/dev/sda4', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachemode': u'writeback', u'cachemetalvsize': u'70G', u'cachelvsize': u'630G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/mapper/vdo_{disklabel}p1\" still in use\n", "item": {"cachedisk": "/dev/sda4", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_{disklabel}p1", "cachelvsize": "630G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_{disklabel}p1", "cachemetalvsize": "70G", "cachemode": "writeback", "cachethinpoolname": "gluster_thinpool_gluster_vg_{disklabel}p1", "vgname": "gluster_vg_{disklabel}p1"}, "msg": "Unable to reduce gluster_vg_{disklabel}p1 by /dev/dm-15.", "rc": 5} somewhere within that I see something that points to a race condition ("still in use"). Unfortunately I have not been able to pinpoint the raw logs which are used at that stage and I wasn't able to obtain more info. At this point quite a bit of storage setup is already done, so rolling back for a clean new attempt, can be a bit complicated, with reboots to reconcile the kernel with data on disk. I don't actually believe it's related to single node and I'd be quite happy to move the creation of the SSD cache to a later stage, but in a VDO setup, this looks slightly complex to someone without intimate knowledge of LVS-with-cache-and-perhaps-thin/VDO/Gluster all thrown into one. Needless the feature set (SSD caching & compressed-dedup) sounds terribly attractive but when things don't just work, it's more terrifying.

5 7

Moving HostedEngine
by Joseph Goldman 28 Nov '19

28 Nov '19

Hi List, In one of my installs, I set up the first storage domain (and where the HostedEngine is) on a bigger NFS NAS - since then I have created a Gluster volume that spans the 3 hosts and I'm putting a few VM's in there for higher reliability (as SAN is single point of failure) namely I'd like to put HostedEngine in there so it stays up no matter what and can help report if issues occur (network issue to NAS, NAS dies etc etc) Looking through other posts and documentation, there's no real way to move the HostedEngine storage, is this correct? The solution I've seen is to backup the hosted engine DB, blow it away, and re-deploy it from the .backup file configuring it to the new storage domain in the deploy script - is this the only process? How likely is this to fail? Is it likely that all VM's and settings will be picked straight back up and continue to operate like normal? I dont have a test setup to play around with atm so just trying to gauge confidence in such a solution. Thanks, Joe

3 3

Migrate VM from oVirt to oVirt
by adrianquintero＠gmail.com 28 Nov '19

28 Nov '19

Hello, What would be the procedure to migrate a VM from oVirt to oVirt? Migrate from oVirt 4.2 running on Site A to oVirt 4.3 Site B. thanks!

5 7

Re: HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Strahil 28 Nov '19

28 Nov '19

The HostedEngine does it automatically, but the option that defines the OVF refresh interval is not accurate. Just power it up without that option (cluster in maintenance) and keep it running for a day. On the next day power it off and try to power it up via hosted-engine --vm-start. Best Regards, Strahil NikolovOn Nov 28, 2019 11:54, Ralf Schenk <rs(a)databay.de> wrote: > > Hello, > > I did something like that via "virsh edit HostedEngine". > > But how is the change written back to the shared storage ("hosted_storage" so it stays permanent for HA Engine ? > > I was able to boot up HostedEngine manually via virsh start after removing the required flag from XML (I first added a user to sasldb in /etc/libvirt/passwd.db to be able to log into libvirt). > > Bye > > > Am 28.11.2019 um 05:51 schrieb Strahil: > > Hi Ralf, > When the deployment fail - you can dump the xml from virsh , edit it, undefine the current HostedEngine and define your modified HostedEngine 's xml. > > Once you do that, you can try to start the > VM. > > Good luck. > > Best Regards, > Strahil Nikolov > > On Nov 27, 2019 18:28, Ralf Schenk <rs(a)databay.de> wrote: >> >> Hello, >> >> This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. >> >> At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. >> >> QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". >> >> Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. >> >> From VM XML: >> >> <cpu mode='custom' match='exact' check='partial'> >> <model fallback='allow'>EPYC</model> >> <topology sockets='16' cores='4' threads='1'/> >> <feature policy='require' name='ibpb'/> >> <feature policy='require' name='virt-ssbd'/> >> >> from cat /proc/cpuinfo: >> >> processor : 47 >> vendor_id : AuthenticAMD >> cpu family : 23 >> model : 49 >> model name : AMD EPYC 7402P 24-Core Processor >> stepping : 0 >> microcode : 0x830101c >> cpu MHz : 2800.000 >> cache size : 512 KB >> physical id : 0 >> siblings : 48 >> core id : 30 >> cpu cores : 24 >> api

1 0

Re: spice connection error
by Strahil 28 Nov '19

28 Nov '19

Check on host 'node3' in the Network configuration if you have a network out of sync or any clues about the error . Best Regards, Strahil NikolovOn Nov 28, 2019 11:44, Kim Kargaard <Kim.Kargaard(a)noroff.no> wrote: > > Hi, > > I am getting the attached error when trying to move the Display from the one network to the other within the cluster. I can't see any place to set an IP for the vnic that I want to set as the display network. > > Any thoughts? > > Kim > > On 28/11/2019, 06:41, "Strahil" <hunter86_bg(a)yahoo.com> wrote: > > As far as I know , the engine plays a role as a proxy during the establishment of the connection. > Check that you can reach both engine and the host from your system. > > For the same reason, I use noVNC - as you just need a single port to the engine in addition to the rest of the settings. > > Best Regards, > Strahil NikolovOn Nov 27, 2019 11:27, kim.kargaard(a)noroff.no wrote: > > > > Hi, > > > > When trying to connect from a remote network on the spice console to a VM, I get the following error: > > > > (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out > > > > I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: > > > > Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. > > > > I am not sure what this means. Any ideas? > > > > Kind regards > > > > Kim > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6YEI3I4NCAHQO… > >

1 0

VDSM Errors see below
by rob.downer＠orbitalsystems.co.uk 28 Nov '19

28 Nov '19

I have removed all deployment of the hosted engine by running the following commands. ovirt-hosted-engine-cleanup vdsm-tool configure --force systemctl restart libvirtd systemctl restart vdsm on my hosts I have the following ovirt 1 is the host I ran the hosted engine setup. I have set the Gluster network to use the same subnet and set up forward and reverse DNS for the Gluster port network NIC's I had this working using a separate subnet but thought to try it on the same subnet to avoid any issues that may have occurred while using a separate network subnet. the main Host IP address is still showing in Unamanaged Connections on Ovirt 1 .. is this anything to be concerned about after running the commands above... I have restarted all machines. All come back with these VDSM errors... Node 1 [root@ovirt1 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2019-11-28 13:29:40 UTC; 37min ago Process: 31178 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS) Process: 30721 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 /dev/null -2 /dev/null /usr/share/vdsm/vdsmd (code=exited, status=0/SUCCESS) Main PID: 30721 (code=exited, status=0/SUCCESS) Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN Not ready yet, ignoring event '|virt|VM_status|871ce9d5-417a-4278-8446-28b681760c1b' args={'871ce9d5-417a-4278-8446-28b681760c1b': {'status': 'Poweri... Nov 28 13:28:43 ovirt1.kvm.private vdsm[30721]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channels/871ce9d5-417a-4278-8446-28b681760c1b.com.redhat.rhevm.vdsm already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channel/target/domain-1-HostedEngineLocal/org.qemu.guest_agent.0 already removed Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available. Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 28 13:29:39 ovirt1.kvm.private systemd[1]: Stopping Virtual Desktop Server Manager... Nov 28 13:29:39 ovirt1.kvm.private vdsmd_init_common.sh[31178]: vdsm: Running run_final_hooks Nov 28 13:29:40 ovirt1.kvm.private systemd[1]: Stopped Virtual Desktop Server Manager. Hint: Some lines were ellipsized, use -l to show in full. [root@ovirt1 ~]# nodectl check Status: WARN Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... BAD NODE 2 [root@ovirt2 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:30 UTC; 1min 13s ago Process: 3626 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 5418 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─5418 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: libvirt: Network Filter Driver error : Network filter not found: no nwfilter with matching name 'vdsm-no-mac-spoofing' Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running dummybr Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running tune_system Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_space Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_lo Nov 28 13:57:30 ovirt2.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available, KSM stats will be missing. [root@ovirt2 ~]# nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK [root@ovirt2 ~]# Node 3 [root@ovirt3 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:08 UTC; 12min ago Process: 2849 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 3220 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─3220 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running nwfilter Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running dummybr Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running tune_system Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_space Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_lo Nov 28 13:57:08 ovirt3.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available, KSM stats will be missing. [root@ovirt3 ~]# nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK [root@ovirt3 ~]#

1 0