This usually means that the volume is corrupted. You could try running the
bls command to see what that reports.
Also check for any syslog messages about disk errors.
__Martin
> On Thu, 22 Sep 2022 20:12:25 +0200, Matlink said:
>
> Hello everyone,
>
> I have an issue when using copy job
Hello everyone,
I have an issue when using copy jobs. I use copy jobs to off-site my
backups to another SD. However, for some volumes I get errors when they
are read (check forwarded mail from bacula):
*Volume data error at 0:0! Short block of 3377 bytes on device
"FileStorage" (/var/sp
On 30/12/18 2:34 pm, Adam Nielsen wrote:
> Any idea what else was upgraded?
https://pastebin.com/raw/ggbV7TkJ contains a complete log of every
package upgraded, downgraded and reinstalled on the server since Bacula
7.4.5.
___
Bacula-users mailing list
Very interesting! Thanks for letting us know about the solution.
> Next I tried a package update (Arch Linux pacman -Syu) and reboot. This
> resolved all issues! This server is kept up-to-date, so the only change
> of significance was a new kernel version (4.19.12).
Any idea what else was upgrad
On 29/12/18 4:41 pm, Adam Nielsen wrote:
> I'd suggest rewinding the tape and writing some EOF marks to
> make the tape look empty, then relabelling it through Bacula. If the
> tape is in good condition, this should allow it to be reused, but of
> course doesn't explain what happened in the first
> Last month I upgraded to Bacula 9.2.2. Backups worked without error but
> I noticed "list volumes" reporting a 25 TB volume (not 6 TB as usual). A
> subsequent test restore failed due to a volume data error.
>
> Downgrading back to Bacula 7.4.5 did not resolve the issue.
It sounds then like thi
I used Bacula 7.4.5 successfully for around 2 years with an IBM
ULTRIUM-HH7 SAS drive and FlexStor II autoloader (Neoseries) on Arch
Linux. Backups and restores worked perfectly.
Last month I upgraded to Bacula 9.2.2. Backups worked without error but
I noticed "list volumes" reporting a 25 TB volu
