I've run into a situation where it appears that bacula isn't releasing 
the tape in the drive.  I've done releases on both drives but it still 
shows one of the tapes from each of the last two backups as being in use 
by drive2.  I'm performing about 20 jobs spread across 18 hosts and 
bacula is balancing the jobs between the two drives successfully.  The 
one odd thing I've noticed is that the catalog job always gets written 
to a new tape.  The catalog job usually gets assigned drive1 (nst0) and 
the tape that ends up being locked to drive2 (MA3004/WA3003) both had 
free space and weren't in use at the time.

Here is the relevant part of status storage from bconsole:

Device status:
Autochanger "SL-10K" with devices:
    "SL-10K-Drive1" (/dev/nst0)
    "SL-10K-Drive2" (/dev/nst1)
Device "SL-10K-Drive1" (/dev/nst0) is not open.
     Drive 0 is not loaded.
Device "SL-10K-Drive2" (/dev/nst1) is not open.
     Drive 1 is not loaded.
====

In Use Volume status:
MA3004 on device "SL-10K-Drive2" (/dev/nst1)
     Reader=0 writers=0 devres=0 volinuse=0
WA3003 on device "SL-10K-Drive2" (/dev/nst1)
     Reader=0 writers=0 devres=0 volinuse=0

Let me know if there is anything else you need from me in order to 
diagnose this further.  It takes some time to duplicate it but I've been 
able to duplicate it every time I do a backup.

-Shad

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users