Op 2013-04-15 om 04:14 schreef Michael Stauffer _g:
> Bacula 3.0.1
>
> Hi,
>
> I'm tantalizingly near the end of a bscan reconstruciton of a catalog over 35
> tapes. You may remember my posts starting mid February - it took a while but
> it
> also turns out both drives in my device had failed,
On 04/12/13 04:47, Leon White wrote:
> That said, I am sticking to manually issuing the commands for now until I at
> least have a full backup completed. I decided not to use Bill's new script
> just yet, mainly because it takes a long time to cycle through all the
> non-mounted drives and disable
autochanger "loaded" command.
> 3991 Bad autochanger command: /usr/libexec/bacula/mtx-changer /dev/sg3
> loaded 1 /dev/nst0 0
> 3991 result="": ERR=Child died from signal 9: Kill, unblockable
> You must correct this error or the Autochanger will not work.
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Be aware that some of the stuff you're talking about is just the last
N jobs that occurred and what their status was. After a time, they
will not be the most recent jobs and will drift off the end of that
listing.
On 04/15/2013 08:32 AM, Kenny Noe wro
ill, unblockable
You must correct this error or the Autochanger will not work.
I enabled debugging in mtx-changer.conf and noticed a lot of not ready
messages like these:
20130415-17:17:17 Doing mtx -f /dev/sg3 load 1 0
20130415-17:18:11 Device /dev/nst0 - not ready, retrying...
20130415-17:18:12 Dev
Dan,
Thanks for the reply. New jobs mostly run OK. I get a few "cancels"
every so often and try to place tracing them down near the top of the Pri
list. I'll investigate further. Came in this mornig and had a few mins to
review the job status and everything is clear / cleaned up. I didn't do
