Tracy R Reed wrote:
Karl Cunningham wrote:
Tracy --
I noticed in the release notes for 1.38.0 the following:
- Note, with gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) on an
AMD64 CPU running 64 bit CentOS4, there is a compiler bug that
generates bad code that causes Bacula to segment fault.
Typically you will see this in the Storage daemon first. The
solution is to compile Bacula ensuring that no optimization is
turned on (normally it is -O2).
I realize you aren't complaining about segfaults but as a test you might
turn off optimization and recompile to see if that makes any difference.
Hah! I am the reason that warning is there. :) That was the first
serious problem I encountered in getting Bacula set up. Kern Sibbald
helped me debug it and suggested I compile without optimization. I did
so and it now works without segfault. I am glad to see the warning made
it into the release notes.
How many files are you backing up? There is a database insert for every
file that gets backed up. Are you sure there isn't a lot of disk
thrashing going on for database IO? What if you temporarily put the
database on your usb disk to see if that makes a difference.
While doing the slow backup, do you see lots of CPU idle time? Is there
significant iowait time?
Karl Cunningham
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
