On 09/01/17 22:39, Alan Brown wrote:
> On 09/01/17 14:47, Charles wrote:
>> ... Bacula shows the tape wth status Error (simply
>> reflecting what the autoloader has told it?).
>
> Are you sure it was the loader which had the critical error?
No
> Most "critical errors" of this kind are bacula attempting to unload a
> locked drive
Confirmed in bacula.log
> (Lesson: issue explicit unlocking commands in your startup sequence)
>
> Or they're an attempt to unload a tape from a drive where the loader has
> lost track of what slot it came from.
>
> (Lesson: issue explicit drive unload commands in your startup sequence.)
Have modified /etc/init.d/bacula-sd (Debian Jessie), adding mt rewoffl and
mtx unload commands immediately before bacula-sd is started.
> ...
> Other than that: update volume={tapelabel} volstatus=append
Done
Many thanks for sharing your insights Alan :)
Comments inline above.
The only wrinkle was with the autoloader. Presumably it marked a tape
in error because Bacula did. Clearing the Bacula status did not clear
the autolodaer status until the tape was loaded to the drive.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
