oom-kill

michabbs

Active Member
May 5, 2020
134
19
38
I have problem with borg backup while trying to back up ~550.000 of small files:

[1576137.653081] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=ns,mems_allowed=0,oom_memcg=/lxc/5011,task_memcg=/lxc/5011/ns/system.slice/cron.service,task=borg,pid=2284332,uid=0 [1576137.653138] Memory cgroup out of memory: Killed process 2284332 (borg) total-vm:2418672kB, anon-rss:2003748kB, file-rss:2944kB, shmem-rss:0kB, UID:0 pgtables:4692kB oom_score_adj:0 [1576141.111381] oom_reaper: reaped process 2284332 (borg), now anon-rss:312kB, file-rss:108kB, shmem-rss:0kB

The container has 2GB of ram and 8GB of swap. Borg seems to ignore swap at all.

In the beginning the container had only 1GB ram and borg was being killed every time during backup process. So I increased ram to 1.5GB and it helped, but after some time, when borg repository grew up, 1.5G became not enough and I increased ram to 2GB. Now 2GB seems to be not enough. What is going on?
I suspect borg deduplication cache might take plenty of ram, but... why is swap ignored? (I dont care if backup process is slow, I only want it to be done...)

Any ideas how to solve the problem in other way than to again increase ram?
 
What did the developer say about it?

Your problem doesn't seem to arise in the operation of Proxmox VE, but in the use of third-party applications or scripts.
 

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!