I upgraded recently to 1.38.2 and while everything appears to be functioning
normally, I've noticed some odd behavior from the file daemon and director.
When the storage daemon hits the maximum spool size limit and starts writing
the data out to tape, both the file and director daemons end up spinning at
100% cpu utilization until the storage daemon is finished and either ends the
job or goes back to spooling more data. I've seen this behavior on both redhat
9 and fedora core 4 systems. I tried stracing it, but strace just shows it as
waiting in select(), so I assume that strace isn't picking the thread that's
doing the work.
Has anyone else seen anything like this, or is it just me?
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
