[ovirt-users] Re: Ovirt 4.2.7 won't start and drops to emergency console
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 work.
Best Regards,
Strahil NikolovOn Oct 1, 2019 03:11, jeremy_tourville(a)hotmail.com wrote:
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: https://access.redhat.com/solutions/3251681
# cd /var/log
# grep -ri gluster_vg1-lvthinpool-tpool
My metadata is 100% full !!!
Now, how do I find out how big my original metadata size was so I can make the new one
the correct size?
_______________________________________________
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/6PI2N24GVWL...