Resize pve-root

[Tomahawk]

Hello All,

I have installed proxmox o.s. on /dev/sda >> Samsung SSD_870_EVO_500 GB Disk and additional /dev/nvme0n1 >> 2TB NVME Sabrent Rocket 4.0 Plus on Intel NUC RNUC11PAHI70000 Core i7 Panther Canyon as below. I would like to extend the pve-root on /dev/sda/ decrising the size from nvme disk which seems to be very little used . Is this possible at all ? If yes how can I do that ? The /dev/sdb is the samba share disk attached. Many thanks for your help in advance!

LVM:

LVM Thin:






root@pve:~# lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID Qxg3Kb-sJYw-Iv2v-WzSE-Pe6T-dXDv-gNJPtc
LV Write Access read/write
LV Creation host, time proxmox, 2022-03-02 21:46:00 +0100
LV Status available
# open 2
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID 819B67-Xu5p-Rpwn-Jtjj-Us7J-zc5P-qk7uLg
LV Write Access read/write
LV Creation host, time proxmox, 2022-03-02 21:46:01 +0100
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3

--- Logical volume ---
LV Name data
VG Name pve
LV UUID Ta1FDd-TJ55-LvS3-FVQy-qDFH-XzWY-WD8qkQ
LV Write Access read/write
LV Creation host, time proxmox, 2022-03-02 21:46:09 +0100
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 0
LV Size <338.36 GiB
Allocated pool data 0.00%
Allocated metadata 0.50%
Current LE 86619
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6

--- Logical volume ---
LV Name nvme
VG Name nvme
LV UUID wREnwq-dr5x-hdNU-cNti-AfF0-CUOv-NXtwxL
LV Write Access read/write (activated read only)
LV Creation host, time pve, 2022-03-02 20:10:55 +0100
LV Pool metadata nvme_tmeta
LV Pool data nvme_tdata
LV Status available
# open 0
LV Size <1.79 TiB
Allocated pool data 0.00%
Allocated metadata 0.15%
Current LE 468708
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8

 

[shanreich]

You cannot add space from the NVME to the pve-root, since they are located in two different volume groups and a logical volume can only get space from one volume group.

There are however still 17 GB of free space in the pve volume group that you could add to the pve-root logical volume.

 

[Tomahawk]

Hello Stefan,

Many thanks for the quick replay! ;-) So I can add the remining 17GB space from the below pve VG and add it to pve-root. How can i reassing it ? I am wondering why I have so many free space on the NVME disk. Did I misconfigured something during the installation ? Maybe I should configure it in different way ?

--- Logical volume ---
LV Name data
VG Name pve
LV UUID Ta1FDd-TJ55-LvS3-FVQy-qDFH-XzWY-WD8qkQ
LV Write Access read/write
LV Creation host, time proxmox, 2022-03-02 21:46:09 +0100
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 0
LV Size <338.36 GiB
Allocated pool data 0.00%
Allocated metadata 0.50%
Current LE 86619
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6



Best regards,
Tom

 

[shanreich]

You should be able to add the remaining space to the root fs via the following commands:

lvextend -l +100%FREE /dev/pve/root
resize2fs /dev/pve/root

As to your question why the nvme is free. What would you expect to be stored there? It seems like you do not have any disks on either data or nvme LV, so obviously there is no space going to be used. Do you have VMs that you want to store on those? Then you would have to check where you stored the disks. If you stored them on local, then those would be located on your pve-root. You would need to move the disks to either local-lvm or nvme storage if you want them to be located there.

 

[Tomahawk]

Thank you Stefan I will try to resize it. Maybe I do not undersand the whole concept of the incredible Proxmox solution. I would like to use the other remining space on NVME if possible also for VM's. For the moment I am storing the disks and VM's on PVE (/dev/sda) but I can't see the possibility to store them on the NVME disk. The "Multimedia" and "Storage" are network shares not used in proxmox purposes.




On the NVME disk I can't see anything and for some reason not able to assign the VM or store:







Is this possible to use this nvme (pve) free space also for VM's ?

 

[shanreich]

Can you post the content of your storage.cfg ?

cat /etc/pve/storage.cfg

 

[Tomahawk]

I am just back sorry for the delay.. Below is the output:

root@pve:~# cat /etc/pve/storage.cfg
cifs: Multimedia
path /mnt/pve/Multimedia
server 192.168.1.xxx
share Multimedia
content images,snippets,backup,rootdir,vztmpl,iso
prune-backups keep-all=1
username xxx

dir: local
path /var/lib/vz
content backup,images,snippets,vztmpl,iso,rootdir
prune-backups keep-all=1

cifs: Storage
path /mnt/pve/Storage
server 192.168.1.xxx
share Storage
content images,snippets,backup,rootdir,vztmpl,iso
prune-backups keep-all=1
username xxx

lvmthin: nvme
thinpool nvme
vgname nvme
content rootdir,images
nodes pve

cifs: samba
path /mnt/pve/samba
server 192.168.1.xxx
share smb
content rootdir,images,snippets,vztmpl,iso,backup
prune-backups keep-all=1
username xxx

 

[shanreich]

The disks are all on the local storage, which is probably also why your pve-root is so full.

You would need to migrate the disks from the local to the nvme storage in order to utilize the NVME. You can do this by clicking on the respective VM and then selecting the Hardware Tab. Then select the disk of the VM and at the top select 'Disk Action' > 'Move Storage' - then move the disk to the nvme storage. Afterwards there should be an additional 'Unused Disk'. After making sure the VM works with the disk on the new storage, you can delete this disk by selecting it and clicking 'Remove'.

For the future, when creating new VMs, make sure you select the appropriate storage for your disks, so they are stored on the correct storage.

 

[Tomahawk]

It works, many thanks Stefan! ;-) There is also the CloudInit Drive and it is not possible to move. I guest it should stay as it is (It contain only 4MB).