 |
Could you test and report if newer version like the actual 22.1.0 show still the same (mis-)behavior? |
|
|
The problem still exists on Ubuntu 20.04 and bareos-client 22.1.1-pre26. Memory consumption risis rapidly until the OOM-Killer comes. (20 GB after 30 minutes) Can we assist in providing logs or traces? Would need a howto for that. |
|
|
Thanks for the feedback, we can't promise when it would be proceed (will be a best effort), but we are interested to try to reproduce this. Please refer to the following page to run and add result of our bareos-support-info tool. https://servicedesk.bareos.com/help/en-us/2-support/3-how-to-use-the-bareos-support-info-sh-tool You certainly want to check our page concerning how to raise debuglevel howto https://servicedesk.bareos.com/help/en-us/2-support/2-how-do-i-set-the-debug-level and the whole debugging chapter from our documentation. if the resulting file is not too large (<2MB) please attach here (can be also made private, password,keys etc being already filtered out by the tool). Otherwise just ask I will open a temporary upload share. The idea is to be able to reproduce it, so the developer will be able to create a proper fix. |
|
|
As we have an interest to discover what happen on your side, our dev's team is also curious to have the following information. Could you report the output of find <your fileset> | wc -c or as an equivalent if you didn't have huge amounts of files after the last full, echo list files jobid=<last full jobid> | bconsole | wc -c If you have a lot of changes you can replay the command for each incremental and summarize the whole. Thanks |
|
|
The last full backup needed 7 days 19:46:26 to backup 101.431.976 files with a total size of 2.56 TB. (just to clarify: it is another system with the same problem.) Top information after 23 minutes of starting the backup job: PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL 1165622 root 20 0 10,1g 10,0g 6884 S 99,3 42,4 4:41.56 /usr/sbin/bareos-fd -f I cancled the job after that. Attached the bareos-support-info. The compressed debug trace log is more than 800 MB. Could you give me a temporary upload share? |
|
|
Hello, The fd will have to store all the path/filename list with 101.431 Files can start to be big especially on long path and file names. You can estimate how much memory you need by counting the size of those string in the file+path table for a given jobid. |
- Anonymous
