Re: Bacula or Drive problem?

Bill Arlofski via Bacula-users <[email protected]> Mon, 16 Jun 2025 14:32:07 +0000

Newsgroups	gmane.comp.bacula.user
Message-ID	<[email protected]>

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. :)

Best regards,
Bill

-- 
Bill Arlofski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

signature.asc (application/pgp-signature, 583 B)