Sadly, this error is still present in v7.0.4.  There is another error, too, 
where there is no writeable media in the tape drive.
Fatal error: spool.c:263 Fatal append error on device "LTO5-2" 
(/dev/tape-admin2): ERR=tape_dev.c:161 Unable to open device "LTO5-2" 
(/dev/tape-admin2): ERR=No medium found
Both of these are a result of race conditions occurring on tape libraries with 
multiple tape drives, one job per drive, and several backup jobs running nearly 
simultaneously.  Frequently, the storage daemon requires a restart in order to 
release the tape drive affected by the error since the SD still sees a running 
job, however, the director has already indicated the error, sent the 
notification, and does not have a running job to cancel.  On a busy system, 
restarting the SD can be problematic, and losing one or more tape drives is 
also a problem.

My question, why isn't Bacula happy with a writeable volume from the same pool 
if one is mounted in the tape drive assigned to a job?

Patti Clark
Linux System Administrator
R&D Systems Support Oak Ridge National Laboratory


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users