On Tuesday 25 July 2006 12:42, Alan Brown wrote:
> 
> 1: What is the current intended behaviour of "update slots"?

The way it currently works.

> 
> I thought it was intended to scan slots and drives without requiring a 
> tape drive unload in 1.38.

I was going to remove the requirement to unload the drive, but the users 
objected to that so it currently unloads the drive you specify.

> 
> Currently it does - which means that changing out tape sets cannot be done 
> unless at least one drive is idle/blocked - problematic in some 
> circumstances, particularly when a large backup is in progress and waiting 
> for this event means the magazine won't be changed out until next business 
> day, or someone has to wait outside office hours until the drive is freed 
> up.

Yes, the current behavior presents certain problem.  

However, users were overwhelmly in favor of keeping the current behavior until 
they have some way within Bacula to unload drives.  Such code does not 
currently exist.

> 
> 
> 2: Are input/output slots being scanned correcttly?
> 
> When running update slots, Bacula sees the correct number of slots, but 
> doesn't seem to recognise tapes in the mailslots (Input/output slots)

I provide a default mtx-changer script, that knows nothing about "mailslots".  
If you want it to handle mailslots, you will probably need to adapt the 
script, and if you can do it in a way that does not break with changers that 
do not have mailslots, I'll be happy to incorporate it.


-------------------------------------------------------------------------
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

Reply via email to