Search results

Thanks for the feedback. This is really a serious problem as it did completely stall the whole machine. The LXC container has two vCPUs allocated and 1GB of RAM, which should be plenty for its normal processes (simple file server). At least as long as file caching etc is allocated to the host...

second part: Jan 5 09:14:08 proxmox kernel: [435636.005047] 175899 total pagecache pages Jan 5 09:14:08 proxmox kernel: [435636.005049] 2247 pages in swap cache Jan 5 09:14:08 proxmox kernel: [435636.005050] Swap cache stats: add 49884, delete 47637, find 441438/447781 Jan 5 09:14:08 proxmox...

After a hard reboot, this is what syslog has recorded: Jan 5 09:14:08 proxmox kernel: [435636.004894] SLUB: Unable to allocate memory on node -1 (gfp=0xd0) Jan 5 09:14:08 proxmox kernel: [435636.004899] cache: kmalloc-128(6:136), object size: 128, buffer size: 128, default order: 0, min...

Ooops, a few minutes later I even get memory allocation failures! Not good. Complete kernel oops. "SLUB: Unable to allocate memory on node -1" and "Possible memory allocation deadlock". System is hanging (100% CPU usage). I guess, I need to pull the plug. Before that happened about 4,3 GB RAM...

Hello I installed 4.1 on a hp microserver with 12GB RAM and a 3TB HDD. I mainly use lxc containers and added a local ZFS storage for these. I noticed extremely bad write performance for these containers. This morning I installed webmin on a debian container. The dpkg install process of the one...