On Thu, Mar 31, 2022 at 1:30 PM Nir Soffer <nsof...@redhat.com> wrote:

> Removing a storage domain requires moving the storage domain to
> maintainance
> and detaching it. In this state oVirt does not use the domain so it is
> safe to remove
> the lvs and vg on any host in the cluster.
> But if you remove the storage domain in engine with:
>     [x] Format Domain, i.e. Storage Content will be lost!
> vdsm will remove all the lvs and the vg for you.
> If you forgot to format the domain when removing it, removing manually
> is fine.
> Nir
Thanks for answering, Nir.
In fact I think I didn't select to format the domain and so the LVM
structure remained in place (I did it some time ago...)
When you write "vdsm will remove all the lvs and the vg for you", how does
vdsm act and work in this case and how does it coordinate the nodes' view
of LVM structures so that they are consistent, with no cluster LVM in place?
I presume it is lvmlockd using sanlock as external lock manager, but how
can I run LVM commands mimicking what vdsm probably does? Or is it
automagic and I need only to run the LVM commands above without worrying
about it?
When I manually remove LVs, VG and PV on the first node, what to do on
other nodes? Simply a
vgscan --config 'devices { filter = ["a|.*|" ] }'
or what?

Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
List Archives: 

Reply via email to