Dear Bob,

I feel stupid. The number of I/E slots could be configured from the 
tape's interface. I reduced their number to just 6 (minimum).
Now it's reported correctly:
Data Transfer Element 1:Full (Storage Element 70 Loaded):VolumeTag = 
ACW965L4

Best Regards,
Spiros Ioannou

3) Yes, all these slots are reported as I/E. I've seen other posts 
describing this problem.

On 23/10/2009 15:37, Bob Hetzel wrote:
> To me this sounds more like something different about your changer 
> that mtx
> cannot account for.
> 1) Do you have all the latest firmware installed on it
> 2) Which version of mtx do you have?  mtx isn't a part of the bacula 
> project,
>    (it's merely bundled/used because it's also open source) but it is 
> still
>    in active (although not frequent) development and they do have a 
> separate
>    mailing list.
> 3) Have you looked at the actual configuration of the library?  Are 
> all these slots
>    internally thought of as import/export?  If so, perhaps you can 
> change that, or talk
>    to the vendor support about why the library isn't tracking tapes 
> the same when in those
>    slots.
>
> Spiros Ioannou wrote:
>> Hello dear developers,
>> We recently bought a Quantum Scalar50 with 76 slots and 2 LTO-4 
>> drivs. These are two Scalar50 units connected together, drives go to 
>> the bottom unit and the other unit serves as extra slots. mtx is 
>> 1.3.12, OS is CentOS 5.3
>>
>> At first, mtx-changer (bacula 3.0.1) didn't recognize most of the 
>> slots because 72 of them are marked as IMPORT/EXPORT except for the 
>> first 4. mtx status:
>> Data Transfer Element 0:Full (Unknown Storage Element 
>> Loaded):VolumeTag = ACW964L4                        Data Transfer 
>> Element 1:Empty
>>       Storage Element 1:Empty
>>       Storage Element 2:Full 
>> :VolumeTag=ACW971L4                              Storage Element 3:Empty
>>       Storage Element 4:Empty
>>       Storage Element 5 IMPORT/EXPORT:Empty
>>       Storage Element 6 IMPORT/EXPORT:Full 
>> :VolumeTag=ACW970L4                        ...
>>       Storage Element 74 IMPORT/EXPORT:Full 
>> :VolumeTag=ACW974L4                              Storage Element 75 
>> IMPORT/EXPORT:Full :VolumeTag=ACW973L4                              
>> Storage Element 76 IMPORT/EXPORT:Full :VolumeTag=ACW972L4  
>> After changing the mtx-changer script to ignore the IMPORT/EXPORT I 
>> realized that the robot doesn't keep correct track of the loaded slot:
>> 1) If the slot gets loaded to a drive directly from an IMPORT/EXPORT 
>> (I/E) slot (i.e. slot >4) then it is reported as coming from a random 
>> free non-I/E slot (1-4) if an empty I/E slot is found. For example if 
>> slot 3 is empty and a load element 70 to drive it gets reported as 
>> coming from slot 3. So when you unload it (with mtx) it goes back to 
>> 3 and not to 70.
>> 2) If all non-I/E slots 1-4 were full when loading a tape from an I/E 
>> slot it is reported as "Unknown storage element" like in the example 
>> above, breaking the "loaded?" command
>>
>> Issuing "label barcodes" fails because bacula thinks drive0 with the 
>> "unknown" element is empty because of the bad parsing. I fear that if 
>> i modify mtx-changer any further to trick it in seeing the unknown 
>> element as a random "empty" slot number, something will break in bacula.
>> Is there a way to make bacula keep track of tapes using just the 
>> barcode labels and ignore slots? I presume this is what happens with 
>> commercial software.
>>
>> Any more thoughts?
>>
>> thank you,
>> -- 
>> Spiros Ioannou
>> Electrical Engineer
>> IT Manager
>> Hellenic National Audiovisual Archive
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>>  
>>
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and 
>> stay ahead of the curve. Join us from November 9 - 12, 2009. Register 
>> now!
>> http://p.sf.net/sfu/devconference
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bacula-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bacula-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to