On Monday 01 August 2005 10:54, Ferdinando Pasqualetti wrote:
> Hello everybody,
> I would like to tell a random strange behaviour in bacula in bacula-sd.
> The storage (and director) system is a RedHat AS 4.0 2 Gb RAM and 4.5 Tb
> raid 5 disks paritioned (ext3) in 1 Tb partitions. Bacula volumes are
> limited to 45 Gb (compressed by client-fd) so that they can fit on one
> SSL2020 cartridge. During normal behaviour one volume is filled in 1 hour
> 40 minutes, and bacula-sd process uses below 5 % of CPU time. Ramdomly it
> happens that time becomes 3-4 times longer, CPU spent in bacula-sd raise to
> 80-90% (mostly in system space). Once the current volume is filled up
> copying continues with normal behavior, maybe to the end of job or maybe it
> switch again in the bad state. Does anyone have any suggestion about what
> to look for?
It would be helpful if you would specify what version of Bacula you are using
as well as the database (though the database does not come into consideration
here).
I have seen this same behavior and have tried to trap it by all kinds of means
and have never succeeded in doing so. I suspect that it has something to do
with a pthreads kernel bug.
My suggestion is when the FD does this, run an strace on it. If your results
are like mine, it will be sitting in a select() statement that is consuming
the whole system.
> Thanks everybody.
>
> Ferdinando Pasqualetti
> G.T.Dati srl
> Tel. 055 7310862
> Fax 055 720143
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
