mtx.log output:

20111229-20:14:56 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:14:56 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:17:17 Parms: /dev/sg4 loaded 1 /dev/nst0 0
20111229-20:17:17 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:17:17 Parms: /dev/sg4 unload 20 /dev/nst0 0
20111229-20:17:17 Doing mtx -f /dev/sg4 unload 20 0
20111229-20:18:04 Parms: /dev/sg4 load 1 /dev/nst0 0
20111229-20:18:04 Doing mtx -f /dev/sg4 load 1 0
20111229-20:19:52 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:19:52 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:23:56 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:23:56 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:24:49 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:24:49 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:29:48 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:29:48 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:32:17 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:32:17 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:32:17 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:32:17 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:32:29 Parms: /dev/sg4 loaded 1 /dev/nst0 0
20111229-20:32:29 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:32:30 Parms: /dev/sg4 load 1 /dev/nst0 0
20111229-20:32:30 Doing mtx -f /dev/sg4 load 1 0
20111229-20:33:53 Parms: /dev/sg4 unload 1 /dev/nst0 0
20111229-20:33:53 Doing mtx -f /dev/sg4 unload 1 0
20111229-20:35:27 Parms: /dev/sg4 slots 0 /dev/nst0 0
20111229-20:35:27 Doing mtx -f /dev/sg4 -- to get count of slots
20111229-20:35:28 Parms: /dev/sg4 list 0 /dev/nst0 0
20111229-20:35:28 Doing mtx -f /dev/sg4 -- to list volumes
20111229-20:35:28 Parms: /dev/sg4 loaded 1 /dev/nst0 0
20111229-20:35:28 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:35:28 Parms: /dev/sg4 load 1 /dev/nst0 0
20111229-20:35:28 Doing mtx -f /dev/sg4 load 1 0
20111229-20:55:00 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-20:55:00 Doing mtx -f /dev/sg4 0 -- to find what is loaded
20111229-20:55:34 Parms: /dev/sg4 slots 0 /dev/nst0 0
20111229-20:55:34 Doing mtx -f /dev/sg4 -- to get count of slots
20111229-20:55:34 Parms: /dev/sg4 list 0 /dev/nst0 0
20111229-20:55:34 Doing mtx -f /dev/sg4 -- to list volumes
20111229-21:05:53 Parms: /dev/sg4 loaded 0 /dev/nst0 0
20111229-21:05:53 Doing mtx -f /dev/sg4 0 -- to find what is loaded






o_0'


On Fri, Dec 30, 2011 at 9:14 AM, ninyo <ninyod...@gmail.com> wrote:

> Mtx status output again :)
>
> root@WILLY-FOG:/etc/bacula# mtx status
>   Storage Changer /dev/changer:1 Drives, 24 Slots ( 1 Import/Export )
> Data Transfer Element 0:Full (Storage Element 1 Loaded)
>       Storage Element 1:Empty
>       Storage Element 2:Full
>       Storage Element 3:Full
>       Storage Element 4:Full
>       Storage Element 5:Full
>       Storage Element 6:Full
>       Storage Element 7:Full
>       Storage Element 8:Full
>       Storage Element 9:Full
>       Storage Element 10:Full
>       Storage Element 11:Full
>       Storage Element 12:Full
>       Storage Element 13:Full
>       Storage Element 14:Full
>       Storage Element 15:Full
>       Storage Element 16:Full
>       Storage Element 17:Empty
>       Storage Element 18:Full
>       Storage Element 19:Full
>       Storage Element 20:Full
>       Storage Element 21:Full
>       Storage Element 22:Full
>       Storage Element 23:Full
>       Storage Element 24 IMPORT/EXPORT:Empty
>
>
> o_0'
>
>
> 2011/12/30 Dietz Pröpper <di...@rotfl.franken.de>
>
>> Dan Langille:
>> > On Dec 29, 2011, at 7:55 AM, ninyo wrote:
>> > > No. Im not working with barcodes....
>> > > o_0'
>> >
>> > Is this because there is no barcode reader or because you don't want to
>> > use the one that is there?
>>
>> He mailed the output of mtx status way up the thread, and it seems to me,
>> that he does not use barcodes.
>> Is mtx-changer supposed to work w/o barcodes anyway?
>>
>> regards,
>>        Dietz
>>
>>
>> ------------------------------------------------------------------------------
>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>> infrastructure or vast IT resources to deliver seamless, secure access to
>> virtual desktops. With this all-in-one solution, easily deploy virtual
>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>>
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to