Hi Peter,
I could be wrong, but I *think* that is the same problem I experienced
when I updated to 2.0.1. Once a job began, my autochanger would not
load the tape it needed. My solution was to add three lines of code to
the /etc/bacula/mtx-changer file on lines 157-159. I added the
following.
if mt -f $device status | grep ONLINE >/dev/null 2>&1; then
mt -f $device offline
fi
So now it looks like this from line 153 to 170.
#
# enable the following line if you need to eject the cartridge
# mt -f $device offline
# sleep 10
if mt -f $device status | grep ONLINE >/dev/null 2>&1; then
mt -f $device offline
fi
${MTX} -f $ctl unload $slot $drive
;;
load)
debug "Doing mtx -f $ctl load $slot $drive"
${MTX} -f $ctl load $slot $drive
rtn=$?
#
# Increase the sleep time if you have a slow device
# or remove the sleep and add the following:
# wait_for_drive $device
Cheers,
Dave
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter
Eisch
Sent: Friday, January 26, 2007 1:24 PM
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] ? Device is BLOCKED waiting for mount of volume
This is a problem since I moved from 1.38.11 to 2.0.1 that I can't seem
to get past. My changer script works from the command line. The btape
'test'
and 'autochanger' work fine from the command line. If I try to run a
job that uses the autochanger it will load the first media and then sit
and wait for Godot. It seems to hate me.
...
Device status:
Autochanger "DSI" with devices:
"SDLT320" (/dev/nrst0)
Device "Repository" (/u1/bacula/repository) is not open.
Device "FileStorage" (/tmp) is not open.
Device "SDLT320" (/dev/nrst0) open but no Bacula volume is currently
mounted.
Device is BLOCKED waiting for mount of volume "OS0001".
Slot 1 is loaded in drive 0.
Total Bytes Read=0 Blocks Read=0 Bytes/block=0
Positioned at File=0 Block=0
====
In Use Volume status:
OS0001 on device "SDLT320" (/dev/nrst0)
====
*
26-Jan 15:16 sname-sd: Please mount Volume "OS0001" on Storage Device
"SDLT320" (/dev/nrst0) for Job Tape.2007-01-26_15.12.38
*
The components are:
# ch0 at scsibus0 target 14 lun 0: <BDT, ThinStor AutoLdr, T16r> changer
removable # ch0: 8 slots, 1 drive, 1 picker, 0 portals # ch0: async,
8-bit transfers
# st0 at scsibus0 target 0 lun 0: <QUANTUM, SDLT320, 5252> tape
removable # st0: density code 73, variable blocks, write-enabled # st0:
sync (25.00ns offset 62), 16-bit (80.000MB/s) transfers
I guess I should note that with 1.38.11 it would at least write the
first tape and then end up in this same state after mounting the second
tape. I can't do an 'mt status' at this point because it seems to be
doing something to the drive, but whatever that is isn't writing.
Ideas?
peter
------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
