Thanks Robert! I think you're on to something. Tried the three commands you
suggested both as root (which the file daemon runs as) and also as the bacula
user (which both the storage daemon and the director run as).
First as root:
[EMAIL PROTECTED] bacula]# mtx -f /dev/sg4 status
Storage Changer /dev/sg4:1 Drives, 10 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = A0000001
Storage Element 1:Empty:VolumeTag=
Storage Element 2:Full :VolumeTag=A0000002
Storage Element 3:Full :VolumeTag=A0000003
Storage Element 4:Full :VolumeTag=A0000004
Storage Element 5:Full :VolumeTag=A0000005
Storage Element 6:Full :VolumeTag=A0000006
Storage Element 7:Full :VolumeTag=A0000007
Storage Element 8:Full :VolumeTag=
Storage Element 9:Full :VolumeTag=A0000009
Storage Element 10:Full :VolumeTag=CLNA0001
[EMAIL PROTECTED] bacula]# ./mtx-changer /dev/sg4 list
Storage Element 2:A0000002
Storage Element 3:A0000003
Storage Element 4:A0000004
Storage Element 5:A0000005
Storage Element 6:A0000006
Storage Element 7:A0000007
Storage Element 8:
Storage Element 9:A0000009
Storage Element 10:CLNA0001
Note that it keeps not seeing the label on the tape in slot 8, even though I've
tried labelling it time and time again.
[EMAIL PROTECTED] bacula]# ./mtx-changer /dev/sg4 slots
10
Yes, that's right. There are indeed 10 slots in this autochanger. (One of
which has a cleaning tape in it.)
Now trying the same commands as the bacula user:
[EMAIL PROTECTED] bacula]# su - bacula
-bash-3.00$ which mtx
/usr/bin/which: no mtx in
(/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin)
OK, it's no longer in the path, so will call with absolute path:
-bash-3.00$ /usr/sbin/mtx -f /dev/sg4 status
Storage Changer /dev/sg4:1 Drives, 10 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = A0000001
Storage Element 1:Empty:VolumeTag=
Storage Element 2:Full :VolumeTag=A0000002
Storage Element 3:Full :VolumeTag=A0000003
Storage Element 4:Full :VolumeTag=A0000004
Storage Element 5:Full :VolumeTag=A0000005
Storage Element 6:Full :VolumeTag=A0000006
Storage Element 7:Full :VolumeTag=A0000007
Storage Element 8:Full :VolumeTag=
Storage Element 9:Full :VolumeTag=A0000009
Storage Element 10:Full :VolumeTag=CLNA0001
But looks like mtx-changer expects to find it in the path.
-bash-3.00$ /etc/bacula/mtx-changer /dev/sg4 list
/etc/bacula/mtx-changer: line 165: mtx: command not found
-bash-3.00$ /etc/bacula/mtx-changer /dev/sg4 slots
/etc/bacula/mtx-changer: line 182: mtx: command not found
Looks like this might be at least part of the problem. Will modify mtx-changer
so it looks for mtx in the right place and see if that helps. Stay tuned...
John J. Felczak
Build & Integration Manager
Siderean Software, Inc.
-----Original Message-----
From: Robert Nelson [mailto:[EMAIL PROTECTED]
Sent: Monday, October 23, 2006 10:51 PM
To: 'John Felczak'; [email protected]
Subject: RE: [Bacula-users] Bacula not loading autochanger (lots more info)
I apologize if you've already supplied this information, but would you mind
attaching the output of the following three commands:
mtx -f /dev/sg4 status
mtx-changer /dev/sg4 list
mtx-changer /dev/sg4 slots
----- Original Message (abridged) -----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Felczak
Sent: Monday, October 23, 2006 3:06 PM
To: [email protected]
Subject: Re: [Bacula-users] Bacula not loading autochanger (lots more info)
Still having the same problem, but after seeing the recent thread about
required information I figured I'd best include the form with the information
requested.
Bacula version: 1.38.9
OS type and version: Fedora Core 4 (Linux)
How was Bacula built/installed? Was installed from rpms by a former sysadmin
from whom I inherited the project.
Concise description of the problem: Bacula doesn't load tapes into autochanger
when it needs them. Instead it keeps prompting to have them manually losded.
Won't even load them with the bconsole mount command.
Just reports mount OK and logs message requesting me to mount the tape. Had
previously posted to the list. Arno suggested I replace all references to
"VXA-Tape" with "VXA-Library" in the director configuration. I've done so, but
the problem still persists.
Bacula output showing the problem:
*messages
23-Oct 13:14 sandy-dir: Start Backup JobId 234,
Job=Sandy.2006-10-23_13.14.17
23-Oct 13:14 sandy-sd: 3301 Issuing autochanger "loaded drive 0" command.
23-Oct 13:14 sandy-sd: 3302 Autochanger "loaded drive 0", result: nothing
loaded.
23-Oct 13:14 sandy-sd: 3301 Issuing autochanger "loaded drive 0" command.
23-Oct 13:14 sandy-sd: 3302 Autochanger "loaded drive 0", result: nothing
loaded.
23-Oct 13:14 sandy-sd: Please mount Volume "A0000001" on Storage Device
"VXA-Drive" (/dev/nst0) for Job Sandy.2006-10-23_13.14.17
Steps to reproduce the problem:
1. Re/Start all 3 bacula daemons. (They and the MySQL DB are all configured to
run as services.) 2. Issue the run command.
3. Select a backup job to run.
4. Once the job has started, check messages.
5. Note that Bacula has requested manual load of volume into drive, rather than
having the autochanger load the drive as it should.
Other information (optional):
Tape drive/autochanger (for tape problems): Exabyte VXA PacketLoader 1x10 1U
with a single VXA-2 tape drive and 10 slots, the last of which contains a
cleaning cartridge.
Have you run btape "test" command?
If I give it the name of the drive's resource it gets in, but fails to load the
tape when I run test:
23-Oct 14:43 btape: 3301 Issuing autochanger "loaded drive 0" command.
23-Oct 14:43 btape: 3302 Autochanger "loaded drive 0", result: nothing loaded.
btape: btape.c:775 Bad status from rewind. ERR=dev.c:678 Rewind error on
"VXA-Drive" (/dev/nst0). ERR=No medium found.
Curiously enough, though, if I run the "autochanger" test it loads the tape
just fine!
I get pretty much the same results if I invoke btape with the drive's physical
device name /dev/nst0. The "test" test only works if a tape is already loaded
in the drive, but the "autochanger" tape loads a tape if the drive is empty.
>From bacula-sd.conf:
********************
Autochanger {
Name = VXA-Library
Device = VXA-Drive
Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg4
}
Device {
Name = VXA-Drive
Media Type = VXA-2
Archive Device = /dev/nst0
Autochanger = YES
Drive Index = 0
Changer Device = /dev/sg4
Offline On Unmount = no
Hardware End of Medium = no
BSF at EOM = yes
Backward Space Record = yes
Fast Forward Space File = yes
TWO EOF = yes
}
>From bacula-dir.conf:
*********************
Storage {
Name = VXA-Library
Address = sandy.siderean.com
Password = <removed>
Device = VXA-Library
MediaType = VXA-2
Autochanger = yes
}
Modified portion of mtx-changer script:
***************************************
# Increase the sleep time if you have a slow device # or remove the sleep and
add the following:
wait_for_drive $device
sleep 15
exit $rtn
;;
list)
debug "Doing mtx -f $ctl -- to list volumes"
make_temp_file
# Enable the following if you are using barcodes and need an inventory
# $(MTX) -f $ctl inventory
# ${MTX} -f $ctl status >${TMPFILE}
# rtn=$?
# cat ${TMPFILE} | grep " *Storage Element [0-9]*:.*Full" | awk "{print
\$3 \\
$4}" | sed "s/Full *\(:VolumeTag=\)*//"
# cat ${TMPFILE} | grep "^Data Transfer Element [0-9]*:Full (Storage
Element \
[0-9]" | awk '{printf "%s:%s\n",$7,$10}'
# rm -f ${TMPFILE} >/dev/null 2>&1
#
# If you have a VXA PacketLoader and the above does not work, try # turning it
off and enabling the following line.
${MTX} -f $ctl status | grep " *Storage Element [0-9]*:.*Full" | sed
"s/*Stor\ age Element //" | sed "s/Full :VolumeTag=//"
exit $rtn
;;
This is after I implemented Arno's earlier suggestion to replace references to
"VXA-Tape" with "VXA-Library" and also some other suggestions for this type of
problem that I found in earlier threads in the list archives.
I also noticed in an earlier thread about a similar problem back in March of
this year, Arno suggested that running the "update slots" command might help.
AL> It is possible that the catalog doesn't have any information about
volumes
AL> available in the autochanger. The easiest resolution in that case is
diong
AL> an 'update slots [scan] storage=Autoloader' in a Bacula console.
This sounded useful, so gave it a try and got the following bizarre output:
*update slots
Using default Catalog name=MyCatalog DB=bacula Automatically selected Storage:
VXA-Library Connecting to Storage daemon VXA-Library at sandy.siderean.com:9103
...
Connecting to Storage daemon VXA-Library at sandy.siderean.com:9103 ...
3306 Issuing autochanger "slots" command.
Device "VXA-Library" has 10 slots.
Connecting to Storage daemon VXA-Library at sandy.siderean.com:9103 ...
3301 Issuing autochanger "loaded drive 0" command.
3302 Autochanger "loaded drive 0", result: nothing loaded.
3306 Issuing autochanger "list" command.
Invalid Slot number: Storage Element 1:A0000001
Invalid Slot number: Storage Element 2:A0000002
Invalid Slot number: Storage Element 3:A0000003
Invalid Slot number: Storage Element 4:A0000004
Invalid Slot number: Storage Element 5:A0000005
Invalid Slot number: Storage Element 6:A0000006
Invalid Slot number: Storage Element 7:A0000007
Invalid Slot number: Storage Element 9:A0000009
Invalid Slot number: Storage Element 10:CLNA0001
No Volumes found to label, or no barcodes.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
