On Thu, Oct 25, 2012 at 11:55 AM, warley <bacula-fo...@backupcentral.com> wrote: > Hi guys! > > Sometimes the mtx gives some errors, like this one: > > root@server1:~# mtx -f /dev/sg2 status > Storage Changer /dev/sg2:1 Drives, 8 Slots ( 0 Import/Export ) > Data Transfer Element 0:Empty > Storage Element 1:Full :VolumeTag=000001L5 > Storage Element 2:Full :VolumeTag=000002L5 > Storage Element 3:Full :VolumeTag=000003L5 > Storage Element 4:Full :VolumeTag=000004L5 > Storage Element 5:Full :VolumeTag=000005L5 > Storage Element 6:Full :VolumeTag=000006L5 > Storage Element 7:Full :VolumeTag=000007L5 > Storage Element 8:Full :VolumeTag=000008L5 > root@server1:~# mtx -f /dev/sg2 load 6 /dev/st0 0 > Loading media from Storage Element 6 into drive 0...mtx: Request Sense: Long > Report=yes > mtx: Request Sense: Valid Residual=no > mtx: Request Sense: Error Code=0 (Unknown?!) > mtx: Request Sense: Sense Key=No Sense > mtx: Request Sense: FileMark=no > mtx: Request Sense: EOM=no > mtx: Request Sense: ILI=no > mtx: Request Sense: Additional Sense Code = 00 > mtx: Request Sense: Additional Sense Qualifier = 00 > mtx: Request Sense: BPV=no > mtx: Request Sense: Error in CDB=no > mtx: Request Sense: SKSV=no > MOVE MEDIUM from Element Address 4102 to 257 Failed > root@server1:~# mtx -f /dev/sg2 status > Storage Changer /dev/sg2:1 Drives, 8 Slots ( 0 Import/Export ) > Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag = 000006L5 > Storage Element 1:Full :VolumeTag=000001L5 > Storage Element 2:Full :VolumeTag=000002L5 > Storage Element 3:Full :VolumeTag=000003L5 > Storage Element 4:Full :VolumeTag=000004L5 > Storage Element 5:Full :VolumeTag=000005L5 > Storage Element 6:Empty > Storage Element 7:Full :VolumeTag=000007L5 > Storage Element 8:Full :VolumeTag=000008L5 > > The first time I run mtx -f /dev/sg2 status. OK > Then run mtx -f /dev/sg2 load 6 /dev/st0 0, and i have an error. > Then lastly run mtx status again and everything seems ok. > I think this error when loading/unloading is causing errors in bacula. > Because the mtx-changer will misinterpret the command. > Is there any way to remove this error? >
I have seen similar when executing mtx commands when the robot is busy. John ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users