Am 24.01.24 um 18:13 schrieb Marco Gaiarin:
24-Jan 17:22 cnpve3-sd JobId 16234: [SI0202] End of Volume "AAJ661L9" at 333:49131 on
device "LTO9Storage0" (/dev/nst0). Write of 524288 bytes got -1.
24-Jan 17:22 cnpve3-sd JobId 16234: Re-read of last block succeeded.
24-Jan 17:22 cnpve3-sd JobId 16234: End of medium on Volume "AAJ661L9"
Bytes=17,846,022,566,912 Blocks=34,038,588 at 24-Jan-2024 17:22.
24-Jan 17:22 cnpve3-sd JobId 16234: 3307 Issuing autochanger "unload Volume
AAJ661L9, Slot 2, Drive 0" command.
24-Jan 17:28 cnpve3-sd JobId 16234: 3995 Bad autochanger "unload Volume AAJ661L9,
Slot 2, Drive 0": ERR=Child died from signal 15: Termination
Results=Program killed by Bacula (timeout)
24-Jan 17:28 cnpve3-sd JobId 16234: 3304 Issuing autochanger "load Volume
AAJ660L9, Slot 1, Drive 0" command.
24-Jan 17:29 cnpve3-sd JobId 16234: 3305 Autochanger "load Volume AAJ660L9, Slot
1, Drive 0", status is OK.
So, unload timeout, but subsequent load command works as expected (and
backup are continuing...).
In the mtx-changer.conf
You can set debug_log=1 to create a mtx.log in ~bacula home dir which should be
/var/lib/bacula.
I'd set debug_level=100 to log everything.
Maybe the offline time is to low. In my opinion I give it simply 900 seconds to
prevent me
from failures the drive needs more time than expected athough almost it needs
less than 60 seconds.
offline_sleep should be 1.
By the way I'm using mtx-changer script for years untouched I found in my one
the parameters won't
be used in the waiting loop:
# The purpose of this function to wait a maximum
# time for the drive. It will
# return as soon as the drive is ready, or after
# waiting a maximum of 900 seconds.
# Note, this is very system dependent, so if you are
# not running on Linux, you will probably need to
# re-write it, or at least change the grep target.
# We've attempted to get the appropriate OS grep targets
# in the code at the top of this script.
#
wait_for_drive() {
i=0
while [ $i -le 900 ]; do # Wait max 900 seconds
if mt -f $1 status 2>&1 | grep "${ready}" >/dev/null 2>&1; then
stinit 2>/dev/null >/dev/null
break
fi
debug $dbglvl "Device $1 - not ready, retrying..."
sleep 1
i=`expr $i + 1`
done
}
By the way I'm not further sure that is still the state in the distributed
mtx-changer script.
Normally I would expect in the while statement something like
while [ ${offline_sleep -eq 1 ] && [ $i -le ${offline_time} ]; do # Wait
max 900 seconds
(untested)
Cheers,
Pierre
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
