Quota in a container

linxlab

New Member
Jan 15, 2024
2
0
1
Hi everyone,

I've been fighting with my proxmox version 8.1.3 for a few days


I created a volume group lvm (local-lvm) and a storage (volume-test) and then created a privileged container, with the quota service active. the result is that inside the container when I try to execute the quota command I receive

Bash:
quota: Cannot stat() mounted device /dev/mapper/local--lvm-vm--100--disk--0: No such file or directory


I'm asking for help because I've tried them all!

Bash:
root@p1:~# lvs
  LV            VG        Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  vm-100-disk-0 local-lvm -wi-ao---- 20.00g                                                  
root@p1:~# vgs
  VG        #PV #LV #SN Attr   VSize  VFree
  local-lvm   1   1   0 wz--n- <1.70t <1.68t

Bash:
root@p1:~# fdisk -l
Disk /dev/nvme0n1: 1.75 TiB, 1920383410176 bytes, 3750748848 sectors
Disk model: SAMSUNG MZQLB1T9HAJR-00007            
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6AA9745C-A2F7-454C-8781-AD2E3BECC63A

Device              Start        End    Sectors  Size Type
/dev/nvme0n1p1       2048    1048575    1046528  511M EFI System
/dev/nvme0n1p2    1048576    3145727    2097152    1G Linux RAID
/dev/nvme0n1p3    3145728  106528767  103383040 49.3G Linux RAID
/dev/nvme0n1p4  106528768  108625919    2097152    1G Linux filesystem
/dev/nvme0n1p5  108625920 3750744063 3642118144  1.7T Linux filesystem
/dev/nvme0n1p6 3750744752 3750748814       4063    2M Linux filesystem


Disk /dev/nvme1n1: 1.75 TiB, 1920383410176 bytes, 3750748848 sectors
Disk model: SAMSUNG MZQLB1T9HAJR-00007            
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DF022AFD-09FC-45C5-9689-05B508ECDE35

Device             Start        End    Sectors  Size Type
/dev/nvme1n1p1      2048    1048575    1046528  511M EFI System
/dev/nvme1n1p2   1048576    3145727    2097152    1G Linux RAID
/dev/nvme1n1p3   3145728  106528767  103383040 49.3G Linux RAID
/dev/nvme1n1p4 106528768  108625919    2097152    1G Linux filesystem
/dev/nvme1n1p5 108625920 3750744063 3642118144  1.7T Linux LVM


Disk /dev/md2: 1022 MiB, 1071644672 bytes, 2093056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md3: 49.26 GiB, 52897513472 bytes, 103315456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/local--lvm-vm--100--disk--0: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
Last edited:
I would add that even a container with "directory" type storage is unable to use quota

this is the result of command quotacheck

Bash:
root@testws:~# quotacheck -cvgua -m
quotacheck: Cannot stat() mounted device /dev/loop0: No such file or directory
quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option.
 
Has anyone solved this? I've just upgraded my Proxmox setup to 8.2.4 and suddenly my privileged containers quotas don't work anymore.

quotacheck -cvgua -m
quotacheck: Cannot stat() mounted device /dev/mapper/pve-vm--104--disk--2: No such file or directory
quotacheck: Cannot stat() mounted device /dev/mapper/pve-vm--104--disk--3: No such file or directory
quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option.

I tried to boot the kernel with the legacy cgroup version, to no avail, both with the new kernel (6.8.8-4-pve) and old (5.15.158-2-pve).

Thanks for any help you can give, as we really need quota support for those containers.
 
Last edited:
I also tried with a brand new privileged container and a new mounted filesystem with the quota option, but I see the same error.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!