Hello!

This would be my first post to this list.  We have deployed three  
bacula installations at the company I work for and it has been working  
fairly well except for one thing:

Whenever we are running a backup job that causes the tape library to  
run out of tapes we usually get sd crashes while labelling (or  
possibly even just inventorying) new tapes.  Sequence as follows:

* Bacula wants to mount a tape for pool foo
* unmount is performed
* Magazine is ejected
* New unlabeled tapes are loaded
* Labeling is requested
* bacula-sd dies

This happens pretty much on every attempt.  I am unsure wether it also  
happens if just an update slots on appendable/purged media is performed.

We have not seen any crashes while labeling or scanning if bacula is  
otherwise idle so defining the jobs so that they are guaranteed not to  
run out of tapes does kind of take care of the problem.

A sysadmin friend who has been dealing with mtx (with bacula and other  
backup software) told me that it may be a bit lacking when it comes to  
error handling and his theory was that the sd may get confused if mtx  
returns something bad.

One common denominator for these systems is that they are using  
Overland 20-slot libraries and we have noticed that if an mtx command  
is issued while a library operation already is in progress we  
typically get a SCSI error in return.  Could this have something to do  
with it?

Any hints would be greatly appreciated.

Best regards,

/Erik Persson

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users