On 12.08.2015 15:17, Andrey Tataranovich wrote:
> On Tue, 11 Aug 2015 15:47:40 +0100
> Martin Simmons <martin AT lispworks DOT com> wrote:
>
>> You could use bls -j with the volume file to scan the whole volume.
> I'm upset with bls behavior - it does not return non zero exit code
> on error and output error messages to stdout instead of stderr.
>
> # bls -j /bacula/backup/Libvirt-0177; echo $?
> bls: butil.c:287 Using device: "/bacula/backup" for reading.
> 12-Aug 16:11 bls JobId 0: Ready to read from volume "Libvirt-0177" on
> device "FileStorage" (/bacula/backup). Volume Record: File:blk=0:196
> SessId=6 SessTime=1438429819 JobId=0 DataLen=161 Begin Job Session
> Record: File:blk=0:64708 SessId=6 SessTime=1438429819 JobId=7462
> Job=Backup_Win2k3.2015-08-02_22.00.00_20 Date=02-Aug-2015 22:18:05
> Level=F Type=B 12-Aug 16:12 bls JobId 0: Error: block.c:318 Volume data
> error at 1:1073721369! Block checksum mismatch in block=83221
> len=64512: calc=91787392 blk=161ef20e
> 0
>
> Is it fixed in newer versions? Currently I'm using 5.2.6.

I don't think any of the SD tools return error status.  They were
originally designed just to be manually run tools.  None of the tools
write to stderr.  Basically they all use most of the daemon code, since 
daemons do not normally have stdin, stdout, and stderr working with
those devices in the tools is a bit awkward.

If you are upset with its behavior, maybe you could fix it and send a
patch -- as long as you are willing to sign an FLA, we would most likely
integrate your patch.

Best regards,
Kern


------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users