[SOLVED] NFS VZ QUOTA file softlimit exceeded

[Raymond Burns]

I have a repeated issue with a Zoneminder container.
This can be easily repeated with any CentOS 6 x64, with Zoneminder 1.26 and above.
Clean installation of a standard VZ always presents the following errors in the CT and Proxmox Host.

kernel: VZ QUOTA: file softlimit exceeded for id=116

My PVE version:

pveversionpve-manager/3.1-24/060bd5a6 (running kernel: 2.6.32-26-pve)

My storage.cfg:

cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content images,iso,vztmpl,rootdir
        maxfiles 0


nfs: OpenFiler
        path /mnt/pve/OpenFiler
        server 192.168.222.150
        export /mnt/vg_nfs/nfs-ext3/nfs-datastore
        options vers=3
        content images,backup,rootdir
        maxfiles 1


nfs: backups01
        path /mnt/pve/backups01
        server 192.168.222.11
        export /vdev1/proxBKUP
        options vers=3
        content backup
        maxfiles 3


nfs: iso01
        path /mnt/pve/iso01
        server 192.168.222.11
        export /vdev1/proxISO
        options vers=3
        content iso
        maxfiles 0


nfs: templates01
        path /mnt/pve/templates01
        server 192.168.222.11
        export /vdev1/proxISO
        options vers=3
        content vztmpl
        maxfiles 0


nfs: Omni01KVM
        path /mnt/pve/Omni01KVM
        server 192.168.222.11
        export /vdev1/proxKVM
        options vers=3
        content images
        maxfiles 0


nfs: Omni1CT
        path /mnt/pve/Omni1CT
        server 192.168.222.11
        export /vdev1/proxCT
        options vers=3
        content rootdir
        maxfiles 0


nfs: Omni2CT
        path /mnt/pve/Omni2CT
        server 192.168.222.12
        export /poolPROX/proxCT
        options vers=3
        content rootdir
        maxfiles 0


nfs: Net30Backup
        path /mnt/pve/Net30Backup
        server 192.168.222.12
        export /poolPROX/BACKUPS
        options vers=3
        content backup
        maxfiles 30


nfs: Omni2KVM
        path /mnt/pve/Omni2KVM
        server 192.168.222.12
        export /poolPROX/proxKVM
        options vers=3
        content images
        maxfiles 0


nfs: backups2
        path /mnt/pve/backups2
        server 192.168.222.12
        export /poolPROX/BACKUPS
        options vers=3
        content rootdir,backup
        maxfiles 3

My 116.conf:

cat /etc/pve/openvz/116.conf
ONBOOT="yes"


PHYSPAGES="0:4096M"
SWAPPAGES="0:1024M"
KMEMSIZE="1861M:2048M"
DCACHESIZE="930M:1024M"
LOCKEDPAGES="2048M"
PRIVVMPAGES="unlimited"
SHMPAGES="unlimited"
NUMPROC="unlimited"
VMGUARPAGES="0:unlimited"
OOMGUARPAGES="0:unlimited"
NUMTCPSOCK="unlimited"
NUMFLOCK="unlimited"
NUMPTY="unlimited"
NUMSIGINFO="unlimited"
TCPSNDBUF="unlimited"
TCPRCVBUF="unlimited"
OTHERSOCKBUF="unlimited"
DGRAMRCVBUF="unlimited"
NUMOTHERSOCK="unlimited"
NUMFILE="unlimited"
NUMIPTENT="unlimited"


# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="104857600:115343360"
DISKINODES="20000000:22000000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"


# CPU fair scheduler parameter
CPUUNITS="1000"
CPUS="4"
HOSTNAME="zwtzone.hcpct2.hc.hctx.net"
SEARCHDOMAIN="hcpct2.hc.hctx.net"
NAMESERVER="10.30.27.160"
NETIF="ifname=eth0,bridge=vmbr1,mac=4E:AD:2A:ED:82:50,host_ifname=veth116.0,host_mac=72:ED:2B:53:42:F0"
VE_ROOT="/var/lib/vz/root/116"
VE_PRIVATE="/mnt/pve/Omni1CT/private/116"
OSTEMPLATE="centos-6-x86_64.tar.gz"

The container was created with 100gb of space. All attached and local storage have more than 100GB available. The CT should be located on Omni1CT

Any help is appreciated. Please let me know what I should do, or if you need any additional info.

 

[mir]

Have you tried adding tcp to the options for the storage?

How many files in total are on the share?

 

[Raymond Burns]

I tried tcp before, but I may have configured it wrong, as it would not mount.
What do you mean by files? It's Zoneminder, so it saves 1000's hours of video in 30 jpg per second per camera. I'm guessing at 7 cameras * 7 days of video * 30 jpg per second = 2,116,800
That's an estimate. Total file usage:

df -hFilesystem            Size  Used Avail Use% Mounted on
/dev/simfs            200G   12G  189G   6% /
none                  2.0G  4.0K  2.0G   1% /dev
none                  2.0G  270M  1.8G  14% /dev/shm

I boosted to 200GB so that the container could be at least operational until I can figure this out

 

[mir]

Number of files is also limited.
DISKINODES="20000000:22000000"

 

[Raymond Burns]

Is there any negative repercussions with
DISKINODES="unlimited"

I'm not sure the proper options, but Zoneminder can easily exceed 2 million files with 30 - 72kB jpeg being saved every second. I would like to be limited by the total size versus the number of days or files.

 

[Raymond Burns]

For others, this helps to see the remaining INODES.
Run this command from the Proxmox host, and replace 123 with your container ID

[COLOR=#000000][FONT=Liberation Mono]vzctl exec 123 df -i[/FONT][/COLOR]

 

[Raymond Burns]

Setting the option to "unlimited" fixed it. Awesome

Sent from my SGH-T989 using Tapatalk

 

[Raymond Burns]

Another failed attempt at a Zoneminder Container.
I have the DISKINODES="unlimited", but now the disk space on the zfsdataset shows higher usage than the vz reports. I'm guessing an inode is a block size, and although the jpegs are only 42kb and the container shows 40GB space used, it actually takes up more Inodes than default. Not sure why the NFS is reporting 1.2TB used for this single container. Looks like it has to be a KVM.

Any suggestions??