I very recently cloned my Proxmox setup to a larger SSD, but I'm getting a weird bit of activity whenever I attempt to resize the lvm.
I feel I'm missing a different command to extend the data pool to the full size of the drive, but I didn't want to punch in random commands willy nilly. I thought I should ask first and see if others had run into this issue.
Any help is greatly appreciated.
Code:
@:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdf 8:80 0 465.8G 0 disk
├─sdf1 8:81 0 1007K 0 part
├─sdf2 8:82 0 512M 0 part
└─sdf3 8:83 0 465.3G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 58G 0 lvm /
├─pve-data_tmeta 253:2 0 2.5G 0 lvm
│ └─pve-data-tpool 253:4 0 161.4G 0 lvm
│ ├─pve-data 253:5 0 161.4G 1 lvm
│ ├─pve-vm--100--disk--0 253:6 0 20G 0 lvm
│ ├─pve-vm--201--disk--0 253:7 0 2G 0 lvm
│ ├─pve-vm--101--disk--0 253:8 0 64G 0 lvm
│ └─pve-vm--104--disk--0 253:9 0 114G 0 lvm
└─pve-data_tdata 253:3 0 161.4G 0 lvm
└─pve-data-tpool 253:4 0 161.4G 0 lvm
├─pve-data 253:5 0 161.4G 1 lvm
├─pve-vm--100--disk--0 253:6 0 20G 0 lvm
├─pve-vm--201--disk--0 253:7 0 2G 0 lvm
├─pve-vm--101--disk--0 253:8 0 64G 0 lvm
└─pve-vm--104--disk--0 253:9 0 114G 0 lvm
@:~# lvextend -l "+100%FREE" /dev/pve/data
New size (41312 extents) matches existing size (41312 extents).
@:~#I feel I'm missing a different command to extend the data pool to the full size of the drive, but I didn't want to punch in random commands willy nilly. I thought I should ask first and see if others had run into this issue.
Any help is greatly appreciated.