Hi Sebastian
That's great, thank you! I'll give it a try when I have the opportunity to
update the director/SD again.
Best regards
Samuel
On Monday, March 25, 2024 at 3:46:42 PM UTC+1 Sebastian Sura wrote:
> Hi Samuel,
>
> i think i managed to reproduce your Problem. I created a fix here if y
Hi Samuel,
i think i managed to reproduce your Problem. I created a fix here if
you want to check it out: https://github.com/bareos/bareos/pull/1745
Kind Regards
Sebastian Sura
Am 04.03.24 um 11:43 schrieb 'Samuel' via bareos-users:
I finally had the chance to restart the storage daemon thi
I finally had the chance to restart the storage daemon this morning in
order to disable autoxflate.
Today's copy jobs that ran afterwards finished without any warning, so I
think it's probably an issue with autoxflate (on replication?). I can also
successfully restore those new copies.
Best reg
Yes, that's right. In this case though it's a consolidated incremental
which was copied. However, the warnings also occur during migration jobs of
consolidated fulls. The warning has never occurred while copying/migrating
a non-consolidated incremental.
This is all working just fine except for
Hi Samuel
i just wanted to make sure i completely understand the situation. You
have an always incremental job with compression
turned on (which algorithm do you use ?) and then you have a copy job
that copies the consolidated full job (on the same sd)
to tape with a device that auto inflates
Hi again.
So, as expected, the warning occurred again when job 94511 was copied (but
also two new warnings for this specific job):
Warning: dird/catreq.cc:608 MD5 digest not same File=3 as attributes=2
Warning: dird/catreq.cc:608 MD5 digest not same File=18 as attributes=17
Warning: dird/catreq.c
Thanks for looking into it!
Hm, there seems to be no file with fileindex=3 in the database for the copy:
Enter SQL query: select * from file where jobid=94146 and fileindex=3;
No results to list.
All files that are being backed up are just regular files, nothing special.
The copy runs locally on
I meant to say File 3 has no stream 1, sorry for the confusion!
Am 23.02.24 um 13:15 schrieb Sebastian Sura:
Hi Samuel
thanks for the gathering this info. Ill look into the bscan issue as
well though i think this might be a known issue.
Regardless, regarding your actual issue: The bscan outp
Hi Samuel
thanks for the gathering this info. Ill look into the bscan issue as
well though i think this might be a known issue.
Regardless, regarding your actual issue: The bscan output shows that
File 3 is missing its attributes (it has no stream 3).
This confuses the director as it never got
Hi Sebastian,
After looking at the logs some more I noticed that all jobs with this
warning have in common that they're using compression (LZ4) and autoxflate
on replication.
Perhaps this combination is still not entirely fixed yet. I'll try
disabling autoxflate in the coming days.
The entire
Hi Samuel,
would it be possible to run bscan with the bsr of that job and the
-r/--list-records option set ?
The output should look like
bscan: stored/bscan.cc:494-0 Record: SessId=1 SessTim=1708427201
FileIndex=-4 Stream=1 len=164
bscan: stored/bscan.cc:494-0 Record: SessId=1 SessTim=1708427
Hi,
I occasionally run into the following warning during copy and migration
jobs:
Warning: dird/catreq.cc:608 MD5 digest not same File=103468 as
attributes=103467
The two indices change with each occurrence, but the file and attribute
index are always off by one.
Does anybody know what thi
12 matches
Mail list logo
