Accidentally typed wrong value when using lvresize

[Firestone]

Hi everyone, and thank you for a fantastic distribution!

I have used ProxMox for a while now on a test server, and it seems to work flawlessly.
Today I decided to add a new harddrive to the system, and in the process of adding the new drive to LVM, I accidentally typed the wrong number when using the lvresize-command. I typed a number a little bit to high.

So I tried to just use the lvreduce command to undo the mistake, but I would then be met by the following error:

root@sulaco:/etc/pve# lvreduce -l 566439 /dev/mapper/pve-data
Thin pool volumes cannot be reduced in size yet.


I recorded the original values before I even started to resize the logical volume, and it looked like this:

root@sulaco:/etc# lvdisplay /dev/mapper/pve-data
--- Logical volume ---
LV Name data
VG Name pve
LV UUID fcPmpi-N4ed-9mAn-uM4E-QM7D-m31W-LjSiY4
LV Write Access read/write
LV Creation host, time proxmox, 2016-11-21 17:48:03 +0100
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 6
LV Size 2.16 TiB
Allocated pool data 3.58%
Allocated metadata 13.42%
Current LE 566439
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 251:4

How can I reverse this process and start over again?

Server is running ProxMox v4.4

 

[NabiKAZ]

I have same this problem with `lvreduce` and `lvresize` about lv pool data:

root@pve:~# lvreduce -L -1G /dev/pve/data
  Thin pool volumes pve/data_tdata cannot be reduced in size yet.

root@pve:~# lvresize -L 7G /dev/pve/data
  Thin pool volumes pve/data_tdata cannot be reduced in size yet.

 

[oguz]

Reducing the size for thinpool volumes has apparently not been implemented in LVM yet.

some info on this: https://www.redhat.com/archives/linux-lvm/2014-March/msg00020.html

How can I reverse this process and start over again?

I'd back everything up, create a new one with the right size and restore everything from there.