Jose,
The report should report the error.
The attached patch fix it.
Jean-Louis
On 01/11/17 12:18 PM, Jose M Calhariz wrote:
On Wed, Nov 01, 2017 at 10:47:10AM -0400, Jean-Louis Martineau wrote:
Jose,
When amanda did the backup, it computed a crc of 6828c030.
But it compute b8d66d3d when it
Hi
I am using amanda 3.5 on my personal server and started to investigate
a strange problem on my amanda installation.
Since around 10 days ago when it runs the amdump during the nigth, it
flush the holdingdisk, by starting allways with the same big DLE.
This means after the DLE is on vTape is
On Wednesday 01 November 2017 10:24:00 Jose M Calhariz wrote:
> Hi
>
> I am using amanda 3.5 on my personal server and started to investigate
> a strange problem on my amanda installation.
>
> Since around 10 days ago when it runs the amdump during the nigth, it
> flush the holdingdisk, by
Jose,
When amanda did the backup, it computed a crc of 6828c030.
But it compute b8d66d3d when it read it from holding disk to flush it.
Do you see that error in the report for all flush attempt?
The holding disk file is not erase because of the crc mismatch.
You can manually remove it (amadmin
On Wed, Nov 01, 2017 at 10:47:10AM -0400, Jean-Louis Martineau wrote:
> Jose,
>
> When amanda did the backup, it computed a crc of 6828c030.
> But it compute b8d66d3d when it read it from holding disk to flush it.
> Do you see that error in the report for all flush attempt?
Yes, I see.
>
>
