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?
Thanks everybody.
Ferdinando Pasqualetti
G.T.Dati srl Tel. 055 7310862 Fax 055 720143 |
- [Bacula-users] Bacula-sd CPU eating in system space... Ferdinando Pasqualetti
- Re: [Bacula-users] Bacula-sd CPU eating in sys... Kern Sibbald