Easiest way to expand pve/root?

S

SomeUser

Member
Aug 1, 2020
24
5
23
55
I have a 1TB drive in my proxmox 8 box (fresh install), using it to test bluestacks (it's a different level of pain...) and I am finding out that with the default installs, I don't have much space for backing up a virtual machine. Tried lvextend and didn't get far. What's the easiest way to expand root, or alternatively, create a 100GB partition for backups of my VM?

Thank you.

Code: 
lvextend /dev/pve/root -L +50g
  Insufficient free space: 12800 extents needed, but only 4096 available
root@gtr:/var/lib/vz/template/iso# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   14G     0   14G   0% /dev
tmpfs                 2.8G  1.5M  2.8G   1% /run
/dev/mapper/pve-root   94G   84G  5.3G  95% /
tmpfs                  14G   46M   14G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
efivarfs              128K   27K   97K  22% /sys/firmware/efi/efivars
/dev/nvme0n1p2       1022M  344K 1022M   1% /boot/efi
/dev/fuse             128M   20K  128M   1% /etc/pve
tmpfs                 2.8G     0  2.8G   0% /run/user/1000
Code: 
root@gtr:/var/lib/vz/template/iso# pvdisplay
  --- Physical volume ---
  PV Name               /dev/nvme0n1p3
  VG Name               pve
  PV Size               930.51 GiB / not usable 4.69 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              238210
  Free PE               4096
  Allocated PE          234114
  PV UUID               JyGOvo-37nA-ruqA-7Iya-MXuO-u9jL-erAPmv
Code: 
root@gtr:/var/lib/vz/template/iso# lsblk -f
NAME                         FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                                                       
├─nvme0n1p1                                                                                                   
├─nvme0n1p2                  vfat        FAT32          9B76-183D                              1021.6M     0% /boot/efi
└─nvme0n1p3                  LVM2_member LVM2 001       JyGOvo-37nA-ruqA-7Iya-MXuO-u9jL-erAPmv               
  ├─pve-swap                 swap        1              ee1825e8-9a6f-4aab-a0b8-4bde077ea6d0                  [SWAP]
  ├─pve-root                 ext4        1.0            4c7b2550-e8c4-4adb-97fe-bcf317f6cd23      5.2G    89% /
  ├─pve-data_tmeta                                                                                           
  │ └─pve-data-tpool                                                                                         
  │   ├─pve-data                                                                                             
  │   ├─pve-vm--100--disk--0                                                                                 
  │   ├─pve-vm--100--disk--1                                                                                 
  │   ├─pve-vm--100--disk--2                                                                                 
  │   ├─pve-vm--101--disk--0                                                                                 
  │   ├─pve-vm--102--disk--0                                                                                 
  │   ├─pve-vm--102--disk--1                                                                                 
  │   ├─pve-vm--103--disk--0                                                                                 
  │   ├─pve-vm--103--disk--1                                                                                 
  │   └─pve-vm--105--disk--0                                                                                 
  └─pve-data_tdata                                                                                           
    └─pve-data-tpool                                                                                         
      ├─pve-data                                                                                             
      ├─pve-vm--100--disk--0                                                                                 
      ├─pve-vm--100--disk--1                                                                                 
      ├─pve-vm--100--disk--2                                                                                 
      ├─pve-vm--101--disk--0                                                                                 
      ├─pve-vm--102--disk--0                                                                                 
      ├─pve-vm--102--disk--1                                                                                 
      ├─pve-vm--103--disk--0                                                                                 
      ├─pve-vm--103--disk--1                                                                                 
      └─pve-vm--105--disk--0
 
Dunuin said:
This is asked again and again. See for example my answer from a few days ago or search the forum for more detailed answers; https://forum.proxmox.com/threads/local-and-local-lvm.138255/post-616604

By the way...bad idea to store your backups on the same disk as your VMs unless you additionally upload them to the cloud or similar.
Click to expand...
Apologies - I did honestly search, but I guess I used wrong keywords. And yes, backups on the same disk is bad. But I'm not doing anything prod.
 
SomeUser said:
And yes, backups on the same disk is bad. But I'm not doing anything prod
Click to expand...
Still the question whats the point of a backup if you lose it together with the working copy when your disk fails? With that "not doing anything prod" mindset you could skip the backups altogether if you don't care so much about your data that you think no proper backup is needed.
 
You have no idea what I am doing. Bluestacks on windows on Proxmox is a pain in the ass. And every time it crashes, it requires a reinstall. So a quick backup and restore is wonderful at keeping all the configs and everything available as I test and try to stabilize my config. Once everything is working the way I want, then obviously an off disk backup will be performed.

If the entire disk fails, oh well, replace disk and start over. Not a big deal.
 
Last edited:
SomeUser said:
And every time it crashes, it requires a reinstall. So a quick backup and restore is wonderful at keeping all the configs and everything available as I test and try to stabilize my config.
Click to expand...
Thats a usecase where I personally would make use of snapshots instead of backups if I just need a fast rollback in case I screw something up.
 
You must log in or register to reply here.
Top Bottom