Issue resizing LXC Container Storage

tokenwizard

New Member
Jul 4, 2024
8
1
3
I have an LXC container running PLEX media server for some years now. I now need to increase the storage available to the rootfs of the container.

I am running Proxmox 8.2.4 on a ZFS RAID-z root file system.

So far, I have tried the usual:
Code:
pct resize 100 rootfs +100G

and

Code:
pct resize 100 rootfs 13600G

as well as

Code:
zfs set quota=13600G rpool/data/subvol-100-disk-0

and after each one of these, if I check the size inside the container, it still shows the rootfs as only being 11T:
Code:
root@plex-server:~# df -h
Filesystem                    Size  Used Avail Use% Mounted on
rpool/data/subvol-100-disk-0   11T   11T   19G 100% /
none                          492K  4.0K  488K   1% /dev
tmpfs                          71G  4.0K   71G   1% /dev/shm
tmpfs                          29G  112K   29G   1% /run
tmpfs                         5.0M     0  5.0M   0% /run/lock

What am I missing here?

Thanks!
 
What say pct df 100?
 
Do a zfs list on your proxmox host and post the result
Code:
root@tandj-homelab:~# zfs list
NAME                                USED  AVAIL  REFER  MOUNTPOINT
rpool                              14.4T  17.0G   153K  /rpool
rpool/ROOT                          172G  17.0G   153K  /rpool/ROOT
rpool/ROOT/pve-1                    172G  17.0G   172G  /
rpool/data                         14.2T  17.0G   243K  /rpool/data
rpool/data/subvol-100-disk-0       12.9T  17.0G  10.7T  /rpool/data/subvol-100-disk-0
rpool/data/subvol-102-disk-0       3.04G  17.0G  3.04G  /rpool/data/subvol-102-disk-0
rpool/data/subvol-103-disk-0       13.0G  7.56G  12.4G  /rpool/data/subvol-103-disk-0
rpool/data/subvol-105-disk-0       2.95G  17.0G  2.95G  /rpool/data/subvol-105-disk-0
rpool/data/subvol-106-disk-0       1.94G  8.40G  1.60G  /rpool/data/subvol-106-disk-0
rpool/data/subvol-107-disk-0        635M  17.0G   635M  /rpool/data/subvol-107-disk-0
rpool/data/subvol-108-disk-0       6.01G  14.4G  5.61G  /rpool/data/subvol-108-disk-0
rpool/data/subvol-111-disk-0       3.99G  17.0G  3.05G  /rpool/data/subvol-111-disk-0
rpool/data/subvol-112-disk-0        103G  17.0G   102G  /rpool/data/subvol-112-disk-0
rpool/data/subvol-115-disk-0       79.4G  17.0G  52.5G  /rpool/data/subvol-115-disk-0
rpool/data/subvol-116-disk-0       35.7G  5.40G  34.6G  /rpool/data/subvol-116-disk-0
rpool/data/subvol-117-disk-0       16.3G  17.0G  16.3G  /rpool/data/subvol-117-disk-0
rpool/data/subvol-118-disk-0       81.4G  17.0G  7.91G  /rpool/data/subvol-118-disk-0
rpool/data/subvol-119-disk-0        817G  17.0G   289G  /rpool/data/subvol-119-disk-0
rpool/data/subvol-200-disk-0       53.1G  17.0G  44.4G  /rpool/data/subvol-200-disk-0
rpool/data/vm-104-disk-0           89.5K  17.0G  89.5K  -
rpool/data/vm-104-disk-1           6.72G  17.0G  6.72G  -
rpool/data/vm-110-disk-0           22.4G  17.0G  22.4G  -
rpool/encrypted                    60.2G  17.0G   332K  /media/encrypted
rpool/encrypted/subvol-113-disk-0  60.2G  17.0G  60.2G  /media/encrypted/subvol-113-disk-0
 
Your zfs pool is almost full, so the subvolume 100 is almost full, too.
Technically pct resize sets the refquota, which limits the space the subvolume can take inside the pool, but your pool is full.
 
Last edited: