You can view all LVs via 'lvs -a' and create a new metadata LV of bigger size.
Of course , lvdisplay -m /dev/gluster_vg1-lvthinpool-tpool_tmeta shoould also
Strahil NikolovOn Oct 1, 2019 03:11, jeremy_tourvi...@hotmail.com wrote:
> vgs displays everything EXCEPT
vgs displays everything EXCEPT gluster_vg1
"dmsetup ls" does not list the VG in question. That is why I couldn't run the
lvchange command. They were not active or even detected by the system.
OK, I found my problem, and a solution:
# cd /var/log
Dear oVirt users,
one thing i still cannot find out, is where the engine gathers the storage=
value from in the /etc/ovirt-hosted-engine/hosted-engine.conf
I suppose it's somewhere in a answers file, but i cannot find it.
Any points are appreciated. hopfully this is the last place where the old
I'm wondering why after upgrading our hosts, when viewing the host details,
it's still showing the OS Description as 184.108.40.206. We are using the oVirt Node.
Shouldn't the OS Description show the version we just upgraded to? I do the
upgrade using the web UI.
OS Version: RHEL - 7 -
What happens when it complain that there is no VGs ?
When you run 'vgs' what is the output?
Also, take a look into
I have the feeling that you need to disable all lvs - not only the thin pool,
but also the thin LVs
I think that there is a special file on the shared storage (something like
OVA) that stores the necessary data.
Have you tried with:
hosted-engine --set-shared-config storage :/engine
hosted-engine --set-shared-config mnt_options
Strahil NikolovOn Sep
1. Open VNC console and check the situation. Just like any other VM.
2. You can get the config via checking the vdsm log on the host where the
system has started properly last time (as current situation is bad, check
previous power up event).
You can save the xml and use that to define the
Thanks very much !
Users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
On 9/29/19 12:54 AM, Nir Soffer wrote:
On Sat, Sep 28, 2019 at 11:04 PM Rik Theys > wrote:
Thank you for your time.
On 9/27/19 4:27 PM, Nir Soffer wrote:
On Fri, Sep 27, 2019, 12:37 Rik Theys
> > Engine reports the block size reported by vdsm. Once we get the system
> > up with your 4k storage domain,
> > we can check that engine reports the right value and update it if needed.
> > I think what you should do is:
> > 1. Backup storage domain metadata
Il giorno ven 27 set 2019 alle ore 17:54 Derek Atkins ha
> On Fri, September 27, 2019 11:46 am, Sandro Bonazzola wrote:
> >> I'm curious what the steps should be going from 4.1.9 / EL7.4 to 4.3.x /
> >> EL7.7? I am pretty sure I need some steps along the way (I doubt I can
Mail list logo