Bill Arlofski via Bacula-users schrieb am 16.06.25 um 16:32:
On 6/15/25 2:19 AM, Dr. Thorsten Brandau via Bacula-users wrote:
As this surprisingly looked more like a changer, despite the error
code=70, I changed the changer path in bacula-sd.conf to / dev//sg8
Then I ran a backup (catalogue to make it quick):
*And to my surprise - the backup worked again. *
Now, this is a big surprise. I would not check the devices if despite
many reboots (both, host and changer) all of a sudden the device is
not correct. To be honest, that would probably be something I would
not have looked into....
heh I had made the assumption that you had checked into this (dev
node changing after reboot), hence my comment about doubting this
could be the issue in your case. :)
It is always the first thing I would point someone to, but I failed to
make that first step in this case. Sorry... And thanks to Udo for
making this verification. :)
But... I don't like seeing the error outputs from the mtx commands
though. I wonder i
f you do:
# mtx -f /dev/sg8 status
# echo $?
And see if mtx is exiting with an exit code other than 0.
This would probably cause issues, especially in my replacement script
since I check for exit codes of all utilities that get called. I'll
see if I can find some time to test a few things here - it's been a
long time since I have even looked at that script. :)
Funny enough, Suse Tumbleweed seem to "skip" from time to time an "sg"
device. I cannot say why it does not, but when I had the problems, sg5
was unpopulated. Now after another reboot, it is populated, so the
changer is back to sg7. Meanwhile I changed the device to the
dev/tape/by-id/ which should not change so fast...
MTX is btw exiting (now) with 0.
Cheers
T
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
