Bug 434654

Summary: weird size of inc tar when slicing
Product: [Applications] kbackup Reporter: Philippe ROUBACH <philippe.roubach>
Component: generalAssignee: Martin Koller <martin>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: the backup profile i use

Description Philippe ROUBACH 2021-03-20 08:45:00 UTC 
SUMMARY


If you don't ask for slicing archive then you get some decent size for inc tar, about 700 MB

If you ask for slicing archive with slice of 20 GB then you get 4 slices of about 20 GB for complete backup and a weird size for inc tars, about 16.6 GB, 17.9 GB for example.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

kde apps 20.12.3
Comment 1 Martin Koller 2021-03-20 09:30:55 UTC 
You can not predict (easily) the size of the "inc" slices, since it's the incremental part which contains only the changes after the last full backup.
Or do you say you have exactly the same preconditions and get different sizes of the inc parts ?
Comment 2 Philippe ROUBACH 2021-03-20 09:55:54 UTC 
Yes the 2 backups are the same backups. The only difference is the slicing or not.

700 MB for an inc tar from Sunday to Monday I can't believe, so many files are modified.

16 GB for an inc tar from Sunday to Monday there is a problem somewhere.
Comment 3 Philippe ROUBACH 2021-03-20 09:57:15 UTC 
Created attachment 136873 [details]
the backup profile i use
Comment 4 Martin Koller 2021-03-20 10:16:59 UTC 
I'd say you check the content of the inc tar files to see if there is something in it which should not be.
Comment 5 Philippe ROUBACH 2021-04-13 05:52:24 UTC 
I made an error. In fact there is no problem.