> Sorry, here is a more complete log:
>
> 19-Jul 03:27 khyber-sd JobId 2235: End of medium on Volume "A0000003"
> Bytes=190,865,525,760 Blocks=2,958,604 at 19-Jul-2008 03:27.
> 19-Jul 03:29 khyber-sd JobId 2235: 3307 Issuing autochanger "unload slot 2, 
> drive 0"
> command.
> 19-Jul 03:30 khyber-sd JobId 2235: 3304 Issuing autochanger "load slot 6, 
> drive 0"
> command.
> 19-Jul 03:32 khyber-sd JobId 2235: 3305 Autochanger "load slot 6, drive 0",
> status is OK.
> 19-Jul 03:32 khyber-sd JobId 2235: 3301 Issuing autochanger "loaded? drive 0" 
> command.
> 19-Jul 03:32 khyber-sd JobId 2235: 3302 Autochanger "loaded? drive 0",
> result is Slot 6.
> 19-Jul 03:32 khyber-sd JobId 2235: Error: block.c:995 Read error on fd=3 at 
> file:blk
> 0:0 on device "VXA3drive" (/dev/nst0). ERR=Input/output error.
> 19-Jul 03:32 khyber-sd JobId 2235: Error: block.c:995 Read error on fd=3 at 
> file:blk
> 0:0 on device "VXA3drive" (/dev/nst0). ERR=Input/output error.
>
> And here is the mtx log at the same time:
>
> 20080719-03:29:25 Parms: /dev/sg3 unload 2 /dev/nst0 0
> 20080719-03:29:25 Doing libTool /dev/sg3 -m d1 s2
> 20080719-03:30:41 libTool unload returned 0
> 20080719-03:30:41 sleeping 5 sec after unload
> 20080719-03:30:46 Parms: /dev/sg3 load 6 /dev/nst0 0
> 20080719-03:30:46 Doing libTool /dev/sg3 -m s6 d1
> 20080719-03:31:12 libTool load returned 0
> 20080719-03:31:12   entered wait_for_drive
> 20080719-03:31:22 1 - mt status for /dev/nst0 returned  IM_REP_EN
> 20080719-03:31:32 2 - mt status for /dev/nst0 returned  IM_REP_EN
> 20080719-03:31:42 3 - mt status for /dev/nst0 returned  BOT ONLINE IM_REP_EN
> 20080719-03:31:42 Elapsed time from load to drive ready: 56
> 20080719-03:31:42 waiting 60 sec before returning
> 20080719-03:32:42 Parms: /dev/sg3 loaded 6 /dev/nst0 0
> 20080719-03:32:42 Doing mtx -f /dev/sg3 status -- to find what is loaded
>
> So you see it did wait until ONLINE.  Then it waited an extra 60 sec for good 
> measure
> before returning. total was 56 sec + 60 sec.
>

Thanks. I see that now. I assume that you are never near the tape
drive when this happens to see if the drive goes online and the starts
processing. I know that vxa drives do some type of error checking at
the beginning of a load.

I am thinking of several possible solutions for this problem (reading
the part tape fsf ... in mtx-changer) but they all seem to have a snag
or two.

Can you modify the mtx-changer script so that after the wait_for_drive
returns successful that it will echo the entire status of the mt
status command to a log? It would be interesting to see what the drive
was doing and if it was anything different than a successful load.

John

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users