Re: dar_manager - incremental backups and removed file

On Tuesday, 16 April 2024 22:29:42 CEST Denis Corbin wrote:
> On 16/04/2024 09:44, J. Roeleveld via Dar-support wrote:> On Monday, 15 
> April 2024 22:56:58 CEST Denis Corbin wrote:
>  >> On 15/04/2024 07:04, J. Roeleveld via Dar-support wrote:

Hi Denis,

> OK, the first problem you reported about dar_manager warning is a bug. 
> Here is what produces the output with all detailed date information (new 
> -x option for dar_manager):

Ok, I'll ignore it for now. :)

> # dar_manager -B 
> database_delete_order_warning/zdata_os_services_binhost_root.dmd -f 
> usr/share/fonts/liberation-fonts/.uuid -x
> Warning: using insecure memory!
>   1       Thu Jun  3 15:32:10 2021 + 341379045 ns  saved     absent
>   2       Thu Jun  3 15:32:10 2021 + 341379045 ns  present   absent
>   3       Thu Jun  3 15:32:10 2021 + 341379045 ns  present   absent
>   4       Thu Jun  3 15:32:10 2021  removed                  absent
> 
> 
> The date at #4 is just lacking the sub-second information, which leads 
> it  to be considered older than the dates at #3 #2 and #1 by 
> approximativement 0.341 s. This is the cause of the warning. I will look 
> at the way the removal date is obtained and why it is lacking the 
> sub-second part, but that's almost harmless as far as I see the 
> consequences. This may be a bug in dar or dar_manager I have to 
> investigate that.
> 
> The second problem is the fact the date of removal (over its lack of 
> precision), is not the last modification date of the parent directory. I 
> also have to investigate that. Same thing here, maybe the problem is in 
> dar or dar_manager but this is also a bug.
> 
> # dar_manager -B 
> database_delete_order_warning/zdata_os_services_binhost_root.dmd -f 
> usr/share/fonts/liberation-fonts -x
> Warning: using insecure memory!
>   1       Thu Jun  3 15:32:10 2021 + 341379045 ns  saved     absent
>   2       Thu Jun  3 15:32:10 2021 + 341379045 ns  present   absent
>   3       Thu Jun  3 15:32:10 2021 + 341379045 ns  present   absent
>   4       Mon Apr  8 08:13:39 2024 + 957335766 ns  present   absent
> #
> > 
> >> Which dar and dar_manager version are used?
> > 
> > 
> > I use version 2.7.13.
> > Am planning on upgrading to 2.7.14 later this month.
> 
> 
> 2.7.14 does not bring any fix related to this problem so
> 2.7.13 is perfectly fine, no worries. You can wait for 2.7.15 with these 
> two bug fixes.

I'll check the changelog and see if there is anything I need.

> >>> I have several systems using the same distribution, but only this
> >>> particular one is showing the problem.
> >>
> >> are they all using the same dar and dar_manager versions?
> > 
> > Yes, they all use the same dar and dar_manager versions.
> 
> thus, maybe the file removal activity is not the same on the other 
> systems? this would explain why dar_manager does not warning the same(?)

It's a file inside the font directories which might not even have existed on 
other systems. (From what I found, it's generated by certain tools which I 
might have actually used on that system at some point)

I don't generally look in the "/usr" tree for random files, so I can't be 
certain on the actual timeline. But that file must have been removed 
automatically.

--
Joost