A
A
akordik2020-09-04 23:59:12
LXC
akordik, 2020-09-04 23:59:12

Proxmox stuck when lxc hdd is 100% full?

Installed Proxmox Virtual Environment 5.2-1
(Linux 4.15.17-1-pve #1 SMP PVE 4.15.17-9 (Wed, 9 May 2018 13:31:43 +0200))
When hdd lxc is 100% full (run out of space allocated for CT), disconnected the container via ssh, because the web stopped responding, after that I was able to log in, but the system information was not loaded, restarted pvestatd, partially gjzdbkcm information? but it was not possible to do something with containers. When requesting the status of the container in the console, the request hung, and did not display the information.
Why was the container able to "put down" the system? Does it make sense to limit the place if, when exceeded, the parent system feels bad, or did I misunderstand somewhere and set it up wrong?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
P
Puma Thailand, 2020-09-05
@opium

And how do you give the place to the containers, if it's just a folder on the disk, then there are no delimitations, since a hack is used there.
All other methods will not allow an overflowing container to affect the system

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question