This is what you said C M Reinehr > Scott, > > I'm rather late to the party, but I have an idea that this might be a RAM > problem or, to be specific, that you are running out of RAM. I encountered > something similar a year or two ago. The good news is that the solution is > simply a matter of adjusting a kernel parameter. The kernel parameter that > I > had to adjust was vm.min_free_kbytes, setting it to 16224 instead of the > default 4060. > > Take a look at your kernel logs while the backup job is running and/or run > vmstat. If this is the problem you will quickly see it. I'm afraid that I > don't remember the details of why this worked or how I chose that > particular > value. I stumbled upon some emails discussing it after googling the > particular kernel error that I was receiving; made the change & then > forgot > about it.
Thanks for the feedback. This is something else to look out, although from a high level this would not appear to be the problem because there is plenty of free physical memory and when backup does not crash the system the swap file is never used. On the other hand, I have run out of ideas, so I am willing to take a look at anything. Thanks for the reply. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
