[Bacula-bugs] [bacula 0000536]: StorageId ignored when selecting volumes on system with multiple autochangers

[<bac...@li...>]

The following bug has been REOPENED.
======================================================================
http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000536
======================================================================
Reported By:                reggie
Assigned To:                kern
======================================================================
Project:                    bacula
Bug ID:                     536
Category:                   Director
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
======================================================================
Date Submitted:             01-27-2006 11:30 PST
Last Modified:              02-06-2006 06:43 PST
======================================================================
Summary:                    StorageId ignored when selecting volumes on system with multiple autochangers
Description: 
When it's time for a job to select its next volume, it prefers tapes that
are already in *any* autochanger, not just the one it is using as its
storage.  If the next volume chosen happens to be in another changer, the
job will use the slot # of the other changer to try and locate the tape in
its assigned changer.  When it finds a tape that it can't use in that slot,
the job blocks.
======================================================================

----------------------------------------------------------------------
 kern - 02-06-2006 06:43 PST 
----------------------------------------------------------------------
Thanks for pointing this out.

I have applied most of your patch to version 1.39.  However, as you noted,
it is not a good thing to reference the director's data in the catalog
routines, and in fact, it will probably fail for the storage daemon.

The StorageId is part of the Media record, so it was rather easy to
reference it there.

Since I don't have two autochangers (nor any attached to my laptop), I
haven't actually tested the fix.  I've also back ported it to 1.38, and
you could potentially download the appropriate branch (Branch-1_38_0).

I'll upload the patch (with a few other things include) to this bug
report, but do not guarantee it at all.

Bug History
Date Modified  Username       Field                    Change              
======================================================================
01-27-06 11:30 reggie         New Bug                                      
01-27-06 11:30 reggie         File Added: diffs                            
01-27-06 11:31 reggie         Bug Monitored: reggie                        
01-30-06 07:07 kern           Assigned To               => kern            
01-30-06 07:07 kern           Status                   new => assigned     
02-06-06 06:43 kern           Bugnote Added: 0001452                       
02-06-06 06:43 kern           Resolution               open => fixed       
02-06-06 06:43 kern           Status                   assigned => resolved
02-06-06 06:43 kern           Resolution               fixed => reopened   
02-06-06 06:43 kern           Status                   resolved => feedback
======================================================================