View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001367 | bareos-core | file daemon | public | 2021-06-28 12:30 | 2021-06-28 12:30 |
Reporter | therm | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Linux | OS | Ubuntu | OS Version | 16.04 |
Summary | 0001367: Potential memory leak in bareos-fd in version 20.0.1 | ||||
Description | On big systems (~17TB Disk with 24million inodes) the bareos-fd is consuming a lot of ram. Restarting the client works in the short run but the problem is there after the next run. I thought the ram usage of the bareos-fd would decrease after all jobs have finished but it doesnt. On the system mentioned above bareos-fd takes 5-8GB of RAM doing nothing. It is a simple file backup with no plugins using accurate mode. The only special is that the partition is split up in multiple jobs. top line: 51768 root 20 0 6462352 5,197g 0 S 0,0 33,2 57:29.76 bareos-fd Any idea how to track this done? | ||||
Tags | No tags attached. | ||||
bareos-master: impact | |||||
bareos-master: action | |||||
bareos-19.2: impact | |||||
bareos-19.2: action | |||||
bareos-18.2: impact | |||||
bareos-18.2: action | |||||
bareos-17.2: impact | |||||
bareos-17.2: action | |||||
bareos-16.2: impact | |||||
bareos-16.2: action | |||||
bareos-15.2: impact | |||||
bareos-15.2: action | |||||
bareos-14.2: impact | |||||
bareos-14.2: action | |||||
bareos-13.2: impact | |||||
bareos-13.2: action | |||||
bareos-12.4: impact | |||||
bareos-12.4: action | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2021-06-28 12:30 | therm | New Issue |