View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001519bareos-coreGeneralpublic2023-03-02 15:022023-09-04 16:25
Reportercolttt Assigned Tobruno-at-bareos  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
PlatformLinuxOSDebianOS Version10
Product Version21.1.6 
Summary0001519: bls exit with wrong exit code if file damagesd
DescriptionI would expect that bls exit with a non-zero exit code if a file is not valid/contains errors, but it always exit with 0:

bls -j /backupdata/0004HD ; echo $?
bls: stored/butil.cc:304-0 Using device: "/backupdata" for reading.
02-Mar 14:56 bls JobId 0: Ready to read from volume "0004HD" on device "FileStorage" (/backupdata).
Volume Record: File:blk=0:196 SessId=373 SessTime=1632137493 JobId=35 DataLen=161
02-Mar 14:56 bls JobId 0: Error: stored/block.cc:335 Volume data error at 3:1530691745!
Block checksum mismatch in block=28070848 len=64512: calc=c8a85150 blk=8ed1c2cb
bls: stored/block.cc:96-0 Dump block with checksum error 5c36fed8: size=64512 BlkNum=28070848
               Hdrcksum=8ed1c2cb cksum=c8a85150
bls: stored/block.cc:110-0 Rec: VId=373 VT=1632137493 FI=359968 Strm=contCOMPRESSED len=35511 p=5c375130
bls: stored/block.cc:110-0 Rec: VId=373 VT=1632137493 FI=359968 Strm=COMPRESSED len=65580 p=5c37dbf3
02-Mar 14:56 bls JobId 0: Releasing device "FileStorage" (/backupdata).
0
Steps To Reproduce- manipulate a backup container file
- run bls -j <BACKUPFILE>
- exit code is zero
 - it should be non zero (1 = programm error, 2 = (could be) file error)
TagsNo tags attached.

Activities

bruno-at-bareos

bruno-at-bareos

2023-09-04 16:25

manager   ~0005364

Hello, while we understand the use case, and would like to support it, we will close this issue, as it will not be fixed by itself.
Either this can become a community contribution with proposing changes as a pull request against our github repo, or it maybe a paid/sponsored development.
If you're willing to do so, please contact sales (at) bareos (dot) com for a quote.

Issue History

Date Modified Username Field Change
2023-03-02 15:02 colttt New Issue
2023-09-04 16:25 bruno-at-bareos Assigned To => bruno-at-bareos
2023-09-04 16:25 bruno-at-bareos Status new => closed
2023-09-04 16:25 bruno-at-bareos Resolution open => won't fix
2023-09-04 16:25 bruno-at-bareos Note Added: 0005364