Hi Robert, this wont help you but our environment was also affected by that. So I can confirm that Tape-Setups (at least our two) stop working if upgrading to Bareos 20. Our setup was Ubuntu 18.04 with Bareos 20. I had to downgrade to 19.2.7 (and restore the database before) to get it working again.
Regards, Dennis -------- Weitergeleitete Nachricht -------- Von: 'Robert@yahoomail' via bareos-users <[email protected] > Antwort an: Robert@yahoomail <[email protected]> An: [email protected] Betreff: Re: [bareos-users] Bareos 20 Datum: Fri, 8 Jan 2021 14:47:14 +0100 Hi everyone,to put some more light on this issue, I started the Storage-Daemon in command line modewith a -d100 applied. I get the following after the first job finished: ...bareos-sd (100): stored/append.cc:80-27 Start append data. res=1bareos-sd (100): stored/acquire.cc:460-27 acquire_append device is tapebareos-sd (100): stored/mount.cc:654-27 Swap unloading slot=65535 "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst)bareos- sd (100): stored/mount.cc:660-27 === set in_use vol=LTO_02bareos-sd (100): stored/mount.cc:670-27 Set swap_dev=NULL for dev="My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) swap_dev="My- LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst)bareos-sd (100): stored/mount.cc:626-27 Must load "My-LTO" (/dev/tape/by-id/scsi- 1IBM_ULTRIUM-TD1_1391028290-nst)bareos-sd (100): stored/autochanger.cc:137-27 Device "My-LTO" (/dev/tape/by-id/scsi- 1IBM_ULTRIUM-TD1_1391028290-nst) is not attached to an autochangerbareos-sd (50): stored/askdir.cc:181-27 >dird CatReq Job=donald-backup.2021-01-08_14.26.37_05 GetVolInfo VolName=LTO_02 write=1bareos-sd (50): stored/askdir.cc:108-27 <dird 1000 OK VolName=LTO_02 VolJobs=13 VolFiles=96 VolBlocks=1326427 VolBytes=85570523136 VolMounts=12 VolErrors=0 VolWrites=1326428 MaxVolBytes=0 VolCapacityBytes=0 VolStatus=Append Slot=0 MaxVolJobs=0 MaxVolFiles=0 InChanger=0 VolReadTime=0 VolWriteTime=5007510880 EndFile=95 EndBlock=657 LabelType=0 MediaId=2 EncryptionKey= MinBlocksize=0 MaxBlocksize=0bareos-sd (50): stored/askdir.cc:140-27 DoGetVolumeInfo return true slot=0 Volume=LTO_02, VolminBlocksize=0 VolMaxBlocksize=0bareos-sd (50): stored/askdir.cc:144-27 setting dcr- >VolMinBlocksize(0) to vol.VolMinBlocksize(0)bareos-sd (50): stored/askdir.cc:147-27 setting dcr->VolMaxBlocksize(0) to vol.VolMaxBlocksize(0)bareos-sd (100): stored/autochanger.cc:137-27 Device "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) is not attached to an autochangerbareos-sd (100): stored/dev.cc:618-27 open dev: type=2 dev_name="My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM- TD1_1391028290-nst) vol=LTO_02 mode=OPEN_READ_WRITEbareos-sd (100): stored/dev.cc:638-27 call OpenDevice mode=OPEN_READ_WRITEbareos-sd (100): backends/generic_tape_device.cc:58-27 Open dev: device is tapebareos-sd (100): backends/generic_tape_device.cc:67-27 Try open "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) mode=OPEN_READ_WRITEbareos-sd (100): backends/generic_tape_device.cc:87-27 Open error on "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) omode=2 oflags=2 errno=16: ERR=Device or resource busybareos-sd (100): backends/generic_tape_device.cc:87-27 Open error on "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) omode=2 oflags=2 errno=16: ERR=Device or resource busy... The last message is repeated many times and Bareos finally aborts after 10 minutes with an error message: 08-Jan 14:39 bareos-sd JobId 27: Warning: stored/mount.cc:275 Open device "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst) Volume "LTO_02" failed: ERR=backends/generic_tape_device.cc:141 Unable to open device "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM- TD1_1391028290-nst): ERR=Device or resource busy Hope someone can use this to identify the root cause. Best regards,Robert Am 07.01.21 um 17:26 schrieb 'Robert@yahoomail' via bareos-users: > Hi folks and a happy new year to all of you.I have a running setup of > Bareos 20 on Ubuntu 20.04 (Focal Fossa) with a LTO drive asstorage > device attached. Once I have an "AlwaysOpen = Yes" in the SD device > descriptionthe backup stops after the first job and the status of the > SD is like the following: > ==== > Device status: > Device "My-LTO" (/dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290- > nst) is not open. Device is being initialized.====== > At this point, Bareos is stuck and I need to cancel all remaining > active jobs and do a "systemctl restart bareos-sd"to continue with > the backup. An "AlwaysOpen=No" works but then, the tape drive is > repositioning thetape to the current position again - not nice. > Previous versions of Bareos handled the "AlwaysOpen=Yes" option > correctand process all the jobs w/o any new tape repositioning in > between.Did I miss something? Any help is appreciated. > Many thanks and best regard,Robert -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/8b8f05435ce25b2a53a6175170e22218929e1393.camel%40googlemail.com.
