Whenever a job fails due to a "network error", the next job finishes without any problem, but all following jobs (within a hour or so) fails with 'Fatal error:..is busy writing on "XXX"' where XXX is the volume name which the finished job was writing on.
So the sequence of events is: - At 22:00 each night jobs to start backing up all machines starts - Job 1-(N-1) finishes without any problem- Job N on client A starts and recycles volume X and starts backing up, but fails with "Fatal error: backup.c:498 Network send error to SD. ERR=Broken pipe" and "SD Bytes Written" is 0. - Job N+1 on client B starts writing on volume X and ends without any problems - Job N+2 on client C starts and recycles volume Z but fails to mount it with error 'Fatal error: acquire.c:263 Wanted Volume "Z", but device "File-1" (/var/bacula/backups/1) is busy writing on "X" .'
- All subsequent jobs fail with same error as N+2- Next evening all scheduled jobs (or even a few hours running a manual job) manages to mount requested volume without any problem
I've seen this problem with all 1.38.x relases and I'm currently running 1.38.11
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
