Hello John, I have run the btape test here in our test environment and I could reproduce your problems.
So this is definitely a problem in the bareos code, I expect it is caused by the storage abstraction layer. This means that you found a bug and we have to get that fixed. I already filed a bug in our bugtracker, see http://bugs.bareos.org/view.php?id=400 In the meantime, I would say if the btape "test" command passes in your environment, everything should be OK to run. What you can do to be sure the "End of Tape" is handled correctly is to restore your first backup that will be written on two tapes. This will definitely show if there should be a problem, but I really do not expect that. Thank you very much for using bareos and helping us to improve it, very best regards, Philipp Am 19.01.2015 um 17:47 schrieb John Bolt: > I have some doubts regarding this btape fill test failure: > > 1) Is it mandatory to pass this test or may I run the bareos system reliably > with this failure? > My full backups will require more than one tape. > > 2) Is it a bareos failure or is it a hardware failure? (or a mix?) > > Thanks > > On Monday, January 19, 2015 at 2:40:14 PM UTC-2, John Bolt wrote: >> Hello Philipp, First of all thanks for your time helping me. >> >> I am runing the bareos-14.2.2-46.1.fc20.i686 and my test machine is a >> Fedora18 (Let me know if >> you believe that this fc20 package is not compatible with Fedora 18). >> bareos-debuginfo, >> bareos-devel and bareos-tools are not installed yet. >> >> I just moved the scsicrypto-sd.so and run the test again. I had set both >> tape streamers to >> "Label Block Size = 64512" and "Maximum Block Size = 64512" and re run the >> tests. Both units >> failed but the messages were a bit different from what I first reported: >> >> # mt -f /dev/st0 eject # mt -f /dev/st0 load # btape -v /dev/st0 Tape block >> granularity is 1024 >> bytes. btape: butil.c:301-0 Using device: "/dev/st0" for writing. btape: >> btape.c:484-0 open >> device "LTO-4 INTERNO" (/dev/st0): OK *readlabel btape: btape.c:536-0 Volume >> label read >> correctly. >> >> Volume Label: Id : Bacula 1.0 immortal VerNo : 11 >> VolName >> : TestVolume1 PrevVolName : VolFile : 0 LabelType : >> VOL_LABEL LabelSize >> : 170 PoolName : Default MediaType : LTO-4 PoolType >> : Backup HostName >> : fedora18.soliton Date label written: 17-Jan-2015 21:01 *fill ... ... Wrote >> block=6495000, >> file,blk=78,3840 VolBytes=419,005,440,000 rate=74.12 MB/s Wrote >> block=6500000, file,blk=78,8840 >> VolBytes=419,328,000,000 rate=74.12 MB/s 19-Jan 14:26 btape JobId 0: End of >> Volume >> "TestVolume1" at 78:10498 on device "LTO-4 INTERNO" (/dev/st0). Write of >> 64512 bytes got -1. >> 19-Jan 14:26 btape JobId 0: Re-read of last block succeeded. btape: >> btape.c:2736-0 Last block >> at: 78:10497 this_dev_block_num=10498 btape: btape.c:2750-0 Block not >> written: >> FileIndex=12788317 blk_block=6501658 Size=206 btape: block.c:96-0 Dump block >> Last block written >> 23b51f0: size=64512 BlkNum=6501657 Hdrcksum=622aa7ef cksum=622aa7ef btape: >> block.c:109-0 >> Rec: VId=1 VT=1421679082 FI=12788313 Strm=contDATA len=29172 p=23ce678 >> btape: block.c:109-0 >> Rec: VId=1 VT=1421679082 FI=12788314 Strm=DATA len=32768 p=23d5878 btape: >> block.c:109-0 Rec: >> VId=1 VT=1421679082 FI=12788315 Strm=DATA len=32768 p=23dd884 >> >> btape: block.c:96-0 Dump block Block not written 23a5300: size=64512 >> BlkNum=6501658 >> Hdrcksum=280d55fd cksum=280d55fd btape: block.c:109-0 Rec: VId=1 >> VT=1421679082 FI=12788315 >> Strm=contDATA len=30256 p=23a53b8 btape: block.c:109-0 Rec: VId=1 >> VT=1421679082 FI=12788316 >> Strm=DATA len=32768 p=23ac9f4 btape: block.c:109-0 Rec: VId=1 >> VT=1421679082 FI=12788317 >> Strm=DATA len=32768 p=23b4a00 btape: btape.c:2771-0 End of tape 78:0. Volume >> Bytes=419,434,960,896. Write rate = 74.06 MB/s btape: btape.c:2336-0 Wrote >> 1000 blocks on >> second tape. Done. Done writing 0 records ... btape: btape.c:2405-0 Wrote >> state file >> last_block_num1=10497 last_block_num2=0 btape: btape.c:2420-0 >> >> 14:26:23 Done filling tape at 78:0. Now beginning re-read of tape ... btape: >> btape.c:2501-0 >> Enter do_unfill 19-Jan 14:26 btape JobId 0: Warning: acquire.c:267 Read >> acquire: Could not >> unserialize Volume label: ERR=label.c:871 Expecting Volume Label, got >> FI=SOS_LABEL Stream=0 >> len=144 >> >> Mount Volume "TestVolume1" on device "LTO-4 INTERNO" (/dev/st0) and press >> return when ready: >> 19-Jan 14:27 btape JobId 0: Warning: acquire.c:267 Read acquire: Could not >> unserialize Volume >> label: ERR=label.c:871 Expecting Volume Label, got FI=SOS_LABEL Stream=0 >> len=144 >> >> Mount Volume "TestVolume1" on device "LTO-4 INTERNO" (/dev/st0) and press >> return when ready: >> 19-Jan 14:30 btape JobId 0: Warning: acquire.c:267 Read acquire: Could not >> unserialize Volume >> label: ERR=label.c:871 Expecting Volume Label, got FI=SOS_LABEL Stream=0 >> len=144 >> >> >> >> >> On Monday, January 19, 2015 at 6:15:58 AM UTC-2, philipp.storz wrote: >>> Hello John, >>> >>> What bareos version are you using? >>> >>> I think that your problem might be a problem related to >>> >>> http://bugs.bareos.org/view.php?id=338 >>> >>> Just move/delete the scsicrypto-sd.so plugin so that it doesnt get loaded, >>> >>> Btape should work then. >>> >>> best regards, >>> >>> Philipp >>> >>> >>> Am 17.01.2015 um 23:36 schrieb John Bolt: >>>> Bareos is failing to complete the btape fill test. I tried it with the "m" >>>> (2 tapes) and >>>> "s" (single tape). The log lines below are for the "s" single tape run. >>>> >>>> I tried multiple times with both LTO units I have, an INTERNAL and AN >>>> EXTERNAL one. I had >>>> tweaked the "Maximum File Size" and "Maximum Block Size" for best >>>> performance. btape test >>>> worked successfully. Only fill is failing. >>>> >>>> I will really appreciate any help provided as these tests are very long (2 >>>> hours each run) >>>> and I do not feel comfortable using a backup system that fails its basic >>>> tests. >>>> >>>> By the way, it may be bug related because I selected "s" (single tape) and >>>> Bareos btape >>>> informed that it wrote on the second tape (see log bellow). >>>> >>>> For this run the bareos-sd.conf contains the following lines: >>>> >>>> Device { Name = "LTO-4 EXTERNAL" Media Type = LTO-4 Archive Device = >>>> /dev/st1 Device Type = >>>> Tape AutomaticMount = yes; # when device opened, read it >>>> AlwaysOpen = yes; >>>> RemovableMedia = yes; RandomAccess = no; Maximum File Size = 5G Label >>>> Block Size = 64512 >>>> Maximum Block Size = 262144 LabelMedia = yes; Changer Device = /dev/st0 >>>> Alert Command = "sh >>>> -c 'tapeinfo -f %c |grep TapeAlert|cat'" Alert Command = "sh -c 'smartctl >>>> -H -l error %c'" >>>> } >>>> >>>> >>>> btape -v /dev/st1 Tape block granularity is 1024 bytes. btape: >>>> butil.c:301-0 Using device: >>>> "/dev/st1" for writing. btape: btape.c:484-0 open device "LTO-4 EXTERNAL" >>>> (/dev/st1): OK >>>> >>>> *label Enter Volume Name: TestVolume1 Wrote Volume label for volume >>>> "TestVolume1". *fill >>>> .... or the complete multiple tape (m) test: (s/m) s Simple test (single >>>> tape) selected. >>>> Wrote Start of Session label. 18:19:02 Begin writing Bareos records to >>>> tape ... Wrote >>>> block=5000, file,blk=1,5000 VolBytes=1,310,720,000 rate=77.10 MB/s Wrote >>>> block=10000, >>>> file,blk=1,10000 VolBytes=2,621,440,000 rate=79.43 MB/s ... ... Wrote >>>> block=1605000, >>>> file,blk=79,7638 VolBytes=420,741,120,000 rate=75.83 MB/s Wrote >>>> block=1610000, >>>> file,blk=79,12638 VolBytes=422,051,840,000 rate=75.85 MB/s 17-Jan 19:51 >>>> btape JobId 0: End >>>> of Volume "TestVolume1" at 79:13746 on device "LTO-4 EXTERNAL" (/dev/st1). >>>> Write of 262144 >>>> bytes got -1. 17-Jan 19:51 btape JobId 0: Re-read of last block succeeded. >>>> btape: >>>> btape.c:2736-0 Last block at: 79:13745 this_dev_block_num=13746 btape: >>>> btape.c:2750-0 Block >>>> not written: FileIndex=12882385 blk_block=1611108 Size=262144 btape: >>>> block.c:96-0 Dump >>>> block Last block written 1c08260: size=262144 BlkNum=1611107 >>>> Hdrcksum=57dd6344 >>>> cksum=57dd6344 btape: block.c:109-0 Rec: VId=1 VT=1421525883 >>>> FI=12882369 Strm=contDATA >>>> len=22408 p=1c7d668 btape: block.c:109-0 Rec: VId=1 VT=1421525883 >>>> FI=12882370 Strm=DATA >>>> len=32768 p=1c82dfc ... ... btape: block.c:109-0 Rec: VId=1 >>>> VT=1421525883 FI=12882376 >>>> Strm=DATA len=32768 p=1cb2e44 btape: block.c:109-0 Rec: VId=1 >>>> VT=1421525883 FI=12882377 >>>> Strm=DATA len=32768 p=1cbae50 >>>> >>>> btape: block.c:96-0 Dump block Block not written 1c08180: size=262144 >>>> BlkNum=1611108 >>>> Hdrcksum=528c3a10 cksum=528c3a10 btape: block.c:109-0 Rec: VId=1 >>>> VT=1421525883 >>>> FI=12882377 Strm=contDATA len=22540 p=1c24f28 btape: block.c:109-0 Rec: >>>> VId=1 >>>> VT=1421525883 FI=12882378 Strm=DATA len=32768 p=1c2a740 ... ... btape: >>>> block.c:109-0 >>>> Rec: VId=1 VT=1421525883 FI=12882385 Strm=DATA len=32768 p=1c62794 btape: >>>> btape.c:2771-0 >>>> End of tape 79:0. Volume Bytes=422,342,295,552. Write rate = 75.78 MB/s >>>> btape: >>>> btape.c:2336-0 Wrote 1000 blocks on second tape. Done. Done writing 0 >>>> records ... btape: >>>> btape.c:2405-0 Wrote state file last_block_num1=13745 last_block_num2=0 >>>> btape: >>>> btape.c:2420-0 >>>> >>>> 19:51:55 Done filling tape at 79:0. Now beginning re-read of tape ... >>>> btape: btape.c:2501-0 >>>> Enter do_unfill 17-Jan 19:52 btape JobId 0: Warning: acquire.c:267 Read >>>> acquire: >>>> label.c:260 Could not reserve volume TestVolume1 on "LTO-4 EXTERNAL" >>>> (/dev/st1) Mount >>>> Volume "TestVolume1" on device "LTO-4 EXTERNAL" (/dev/st1) and press >>>> return when ready: >>>> Mount Volume "TestVolume1" on device "LTO-4 EXTERNAL" (/dev/st1) and press >>>> return when >>>> ready: >>>> >>>> The "TestVolume1" IS ALREADY mounted on device "LTO-4 EXTERNAL" (/dev/st1) >>>> but bareos btape >>>> does not accept it anymore. >>>> >>> >>> >>> -- Mit freundlichen Grüßen >>> >>> Philipp Storz Bareos GmbH & Co. KG Phone: Phone: >>> +49221630693-92 >>> http://www.bareos.com Fax: +49221630693-10 >>> >>> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Geschäftsführer: >>> Stephan Dühr, M. >>> Außendorf, J. Steffens, P. Storz, M. v. Wieringen > -- Mit freundlichen Grüßen Philipp Storz [email protected] Bareos GmbH & Co. KG Phone: Phone: +49221630693-92 http://www.bareos.com Fax: +49221630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
