LXC fails to start with quota enabled

minorisa

New Member
Feb 14, 2017
2
0
1
43
Hello,

I am trying to enable quotas for LXC containers on a 4.4 up to date Proxmox VE node.

Containers do not start when quotas are enabled, neither on privileged or unprivileged containers.
I've tried with all Centos, Debian and Ubuntu template versions (except for Ubuntu 16.10) with all of the templates being up to date.

Storage backend is and external CEPH cluster to Proxmox.

Once I disable quotas containers launch correctly.

Here is the output of the following commands run on one of the containers (Ubuntu 16.04):
  • pct config 152
  • pct start 152
  • lxc-start -lDEBUG -o /tmp/log -F -n 152
  • /tmp/log file generated by lxc-start is attached

pct config 152:
Code:
arch: amd64
cores: 1
description:
hostname: test-ubuntu16
memory: 512
net0: name=eth0,bridge=vmbr0,hwaddr=DE:2B:81:40:C9:24,ip=192.168.0.152/24,tag=130,type=veth
ostype: ubuntu
rootfs: ceph-ssd:vm-152-disk-1,quota=1,size=8G
swap: 512

pct start 152:
Code:
lxc-start: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.
command 'lxc-start -n 152' failed: exit code 1

lxc-start -lDEBUG -o /tmp/log -F -n 152:
Code:
mknod: '/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/rbd42': Invalid argument
command 'mknod -m 666 /usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/rbd42 b 8442 160' failed: exit code 1
lxc-start: conf.c: run_buffer: 405 Script exited with status 1.
lxc-start: conf.c: lxc_setup: 3903 failed to run autodev hooks for container '152'.
lxc-start: start.c: do_start: 811 Failed to setup container "152".
lxc-start: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 3)
lxc-start: start.c: __lxc_start: 1365 Failed to spawn container "152".
2017-02-14 12:44:19.744039 7f62d917c780 -1 did not load config file, using default settings.
rbd: failed to remove rbd device: (16) Device or resource busy
can't unmap rbd volume vm-152-disk-1: rbd: failed to remove rbd device: (16) Device or resource busy
volume deactivation failed: ceph-ssd:vm-152-disk-1 at /usr/share/perl5/PVE/Storage.pm line 1028.
lxc-start: tools/lxc_start.c: main: 371 The container failed to start.
lxc-start: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --logpriority options.

/tmp/log file generated by lxc-start is attached.

Any help would be very appreciated.
 

Attachments

  • log.txt
    14.9 KB · Views: 1
Applied some PVE system updates that appeared today and tried again to enable quota on test containers.

It works right now with privileged containers.

Great.
 
Found this thread, I was tried to add quota to an unprivileged container.
Is it possible to restrict enabling quota on unprivileged containers?
 

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!