Menu
▾
▴
Re: [Bacula-users] autochanger problems
|
From: Deric A. <da...@ga...> - 2007-05-31 19:10:07
|
Ok, fixed the problem, thanks for you help though. It helped me
understand how the mtx-changer script works. Because it dumps the
output of mtx to a temp file, and we were out of disk space on that
drive, it would create the temp file but nothing would be in it so
nothing to parse. Anyway fixed, thanks again,
Deric
On Thu, 2007-05-31 at 08:17 -0600, Deric Abel wrote:
> Ok I reviewed all of the things you suggested, here is what I found.
>
> The output from the mtx-changer script is:
>
>
> [root@ganymede bacula]# ./mtx-changer /dev/sg0 list
> 5:000027
> 7:000025
> 8:000024
> 11:000017
> 12:000018
> 13:000019
> 14:000020
> 15:000021
> 16:000022
> 17:000009
> 18:000010
> 19:000011
> 20:000012
> 21:000016
> 22:000003
> 23:000015
> 6:000026
>
> so it is working.....
>
> in my bacula-fd.conf the changer/mtx-changer is
>
> Autochanger {
> Name = Autochanger
> Device = Drive-1, Drive-2
> Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
> Changer Device = /dev/sg0
> }
>
> in the mtx-changer script mtx is :
>
> MTX=mtx
>
>
> I don't think it's the mtx-changer script, because it works when called
> out side of bconsole.
>
> I commented out a part in the mtx-changer script where it deletes the
> temp file that is created from them output of mtx status, and I've found
> what may be causing my problem, but I don't know where to go from
> here...
>
> If I run the script(mtx-changer) from outside bconsole, the file is
> created with the following inside:
>
> Storage Changer /dev/sg0:2 Drives, 23 Slots ( 0 Import/Export )
> Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag =
> 000026
> Data Transfer Element 1:Empty
> Storage Element 1:Empty:VolumeTag=
> Storage Element 2:Empty:VolumeTag=
> Storage Element 3:Empty:VolumeTag=
> Storage Element 4:Empty:VolumeTag=
> Storage Element 5:Full :VolumeTag=000027
> Storage Element 6:Empty:VolumeTag=
> Storage Element 7:Full :VolumeTag=000025
> Storage Element 8:Full :VolumeTag=000024
> Storage Element 9:Empty:VolumeTag=
> Storage Element 10:Empty:VolumeTag=
> Storage Element 11:Full :VolumeTag=000017
> Storage Element 12:Full :VolumeTag=000018
> Storage Element 13:Full :VolumeTag=000019
> Storage Element 14:Full :VolumeTag=000020
> Storage Element 15:Full :VolumeTag=000021
> Storage Element 16:Full :VolumeTag=000022
> Storage Element 17:Full :VolumeTag=000009
> Storage Element 18:Full :VolumeTag=000010
> Storage Element 19:Full :VolumeTag=000011
> Storage Element 20:Full :VolumeTag=000012
> Storage Element 21:Full :VolumeTag=000016
> Storage Element 22:Full :VolumeTag=000003
> Storage Element 23:Full :VolumeTag=000015
>
>
> This is normal I'm assuming.
>
> However, if I issue the command update slots with in bconsole, a temp
> file is created, but is empty, so the parsing is failing there.
>
> Also I enabled debugging with in the mtx-changer script and when I issue
> the update command in bconsole, I see the following in the debug file.
>
> 20070531-07:09:18 Parms: /dev/sg0 slots 0 /dev/nst0 0
> 20070531-07:09:18 Doing mtx -f /dev/sg0 -- to get count of slots
> 20070531-07:09:20 Parms: /dev/sg0 list 0 /dev/nst0 0
> 20070531-07:09:20 Doing mtx -f /dev/sg0 -- to list volumes
>
> Still the same message in bconsole
>
> No Volumes found to label, or no barcodes.
>
> So I tried mtx-change with the parms from the debug file and I get...
>
> # /etc/bacula/mtx-changer /dev/sg0 slots 0 /dev/nst0 0
> 23
>
> # /etc/bacula/mtx-changer /dev/sg0 list 0 /dev/nst0 0
> 5:000027
> 7:000025
> 8:000024
> 11:000017
> 12:000018
> 13:000019
> 14:000020
> 15:000021
> 16:000022
> 17:000009
> 18:000010
> 19:000011
> 20:000012
> 21:000016
> 22:000003
> 23:000015
> 6:000026
>
> Which correct. Any ideas?
>
> Thanks for you help...
>
> Deric
>
> On Wed, 2007-05-30 at 21:41 +0200, Arno Lehmann wrote:
> > Hi,
> >
> > On 5/30/2007 5:52 PM, Deric Abel wrote:
> > > Hello, I've been running 2.0.3 now for a few months and today we have a
> > > problem that I can not resolve.
> > >
> > > We have a tape library with 24 slots. When I do an update slots on
> > > bconsole I get this output:
> > >
> > > *update slots
> > > Automatically selected Catalog: MyCatalog
> > > Using Catalog "MyCatalog"
> > > The defined Storage resources are:
> > > 1: File
> > > 2: Autochanger
> > > Select Storage resource (1-2): 2
> > > Connecting to Storage daemon Autochanger at ganymede:9103 ...
> > > Enter autochanger drive[0]:0
> > > Connecting to Storage daemon Autochanger at ganymede:9103 ...
> > > 3306 Issuing autochanger "slots" command.
> > > Device "Autochanger" has 23 slots.
> > > Connecting to Storage daemon Autochanger at ganymede:9103 ...
> > > 3306 Issuing autochanger "list" command.
> > > No Volumes found to label, or no barcodes.
> >
> > Ok, quite obvious...
> > >
> > > Which isn't right, because a: mtx -f /dev/sg0 status does the following:
> > >
> > > [root@ganymede bacula]# mtx -f /dev/sg0 status
> > > Storage Changer /dev/sg0:2 Drives, 23 Slots ( 0 Import/Export )
> > > Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag =
> > > 000026
> >
> > ... up to this point.
> >
> > > Data Transfer Element 1:Empty
> > > Storage Element 1:Empty:VolumeTag=
> > > Storage Element 2:Empty:VolumeTag=
> > > Storage Element 3:Empty:VolumeTag=
> > > Storage Element 4:Empty:VolumeTag=
> > > Storage Element 5:Full :VolumeTag=000027
> > > Storage Element 6:Empty:VolumeTag=
> > > Storage Element 7:Full :VolumeTag=000025
> > > Storage Element 8:Full :VolumeTag=000024
> > > Storage Element 9:Empty:VolumeTag=
> > > Storage Element 10:Empty:VolumeTag=
> > > Storage Element 11:Full :VolumeTag=000017
> > > Storage Element 12:Full :VolumeTag=000018
> > > Storage Element 13:Full :VolumeTag=000019
> > > Storage Element 14:Full :VolumeTag=000020
> > > Storage Element 15:Full :VolumeTag=000021
> > > Storage Element 16:Full :VolumeTag=000022
> > > Storage Element 17:Full :VolumeTag=000009
> > > Storage Element 18:Full :VolumeTag=000010
> > > Storage Element 19:Full :VolumeTag=000011
> > > Storage Element 20:Full :VolumeTag=000012
> > > Storage Element 21:Full :VolumeTag=000016
> > > Storage Element 22:Full :VolumeTag=000003
> > > Storage Element 23:Full :VolumeTag=000015
> > >
> > >
> > > I have restarted bacula as well as the whole machine, and nothing seems
> > > to fix the problem. Does anyone have any ideas? We are dead in the
> > > water right now.
> >
> > Debugging mtx-changer seems to be necessary.
> >
> > Look at your changer command definition, and use mtx-changer accordingly
> > from the shell. As necessary, add debug output, or run with the -x
> > switch, for example.
> >
> > I suppose that mtx-changer either uses the wrong mtx program which
> > doesn't report volume tags, or can't correctly parse the output of mtx.
> > Both would be fixable.
> >
> > A work-arount would be to use 'update slots scan' in bconsole.
> >
> > Arno
> >
> > > Thanks,
> > >
> > > Deric
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by DB2 Express
> > > Download DB2 Express C - the FREE version of DB2 express and take
> > > control of your XML. No limits. Just data. Click to get it now.
> > > http://sourceforge.net/powerbar/db2/
> > > _______________________________________________
> > > Bacula-users mailing list
> > > Bac...@li...
> > > https://lists.sourceforge.net/lists/listinfo/bacula-users
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users
|