LVM-Thin problem remove VG/LV

[antoniormjr]

Hi, I'm trying to delete LV and VG after thin presenting corrupted data, but I'm not getting it. Here are some errors.
Inactive '/ dev / vmslnxg2 / thinvmslnxg2' [1.39 TiB] inherit
Inactive '/ dev / vmslnxg2 / vm-102-disk-1' [18.00 GiB] inherit
Inactive '/ dev / vmslnxg2 / vm-103-disk-1' [38.00 GiB] inherit

Lnx10: ~ # lvdisplay vmslnxg2 / thinvmslnxg2
--- Logical volume ---
LV Name thinvmslnxg2
VG Name vmslnxg2
LV UUID T8udDp-UtHw-F2iX-APxw-5kTH-W5lk-ZrEcUJ
LV Write Access read / write
LV Creation host, time asunlnx5, 2017-01-29 16:33:59 -0200
LV Pool metadata thinvmslnxg2_tmeta
LV pool data thinvmslnxg2_tdata
LV Status NOT available
LV Size 1.39 TiB
Current LE 364497
Segments
Allocation inherit
Read ahead sectors auto

Lnx10: ~ # lvremove / dev / vmslnxg2 / vm-102-disk-1
Do you really want to remove and DISCARD logical volume vm-102-disk-1? [Y / n]: y
Thin pool transaction_id is 0, while expected 12.
Failed to update pool vmslnxg2 / thinvmslnxg2.

Lnx10: ~ # lvremove -f / dev / vmslnxg2 / thinvmslnxg2
Thin pool transaction_id is 0, while expected 12.
Failed to update pool vmslnxg2 / thinvmslnxg2.

Lnx10: ~ # pveversion -verbose
Proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve)
Pve-manager: 4.4-5 (running version: 4.4-5 / c43015a5)
Pve-kernel-4.4.6-1-pve: 4.4.6-48
Pve-kernel-4.4.13-1-pve: 4.4.13-56
Pve-kernel-4.4.35-2-pve: 4.4.35-78
Pve-kernel-4.4.19-1-pve: 4.4.19-66
Lvm2: 2.02.116-pve3
Corosync-pve: 2.4.0-1
Libqb0: 1.0-1
Pve-cluster: 4.0-48
Qemu-server: 4.0-102
Pve-firmware: 1.1-10
Libpve-common-perl: 4.0-85
Libpve-access-control: 4.0-19
Libpve-storage-perl: 4.0-71
Pve-libspice-server1: 0.12.8-1
Vncterm: 1.2-1
Pve-docs: 4.4-1
Pve-qemu-kvm: 2.7.1-1
Pve-container: 1.0-90
Pve-firewall: 2.0-33
Pve-ha-manager: 1.0-38
Ksm-control-daemon: 1.2-1
Glusterfs-client: 3.5.2-2 + deb8u3
Lxc-pve: 2.0.6-5
Lxcfs: 2.0.5-pve2
Creu: 1.6.0-1
Novnc-pve: 0.5-8
Smartmontools: 6.5 + svn4324-1 ~ pve80
Zfsutils: 0.6.5.8-pve13-bpo80

 

[antoniormjr]

Hi everyone, I solved the problem by following the steps below.

Vgcfgbackup -f vg.bak vgname

// edit vg.bak and remove all thinp related volumes

Vgcfgrestore -f vg.bak vgname

 

[maxprox]

Hi,
I am wondering that this work for you,
as we can read in this manpages

...
lvremove of thin pool LVs, thin LVs and snapshots cannot be reversed
with vgcfgrestore.
...
vgcfgbackup does not back up thin pool metadata.
....

this should not work with LVM-thin (?)