https://bugs.kde.org/show_bug.cgi?id=464712
Bug ID: 464712
Summary: KBackup archives cannot be restored. - tar files are
corrupt
Classification: Applications
Product: kbackup
Version: 22.12.1
Platform: Neon
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: kol...@aon.at
Reporter: jpha...@gmail.com
Target Milestone: ---
Created attachment 155538
--> https://bugs.kde.org/attachment.cgi?id=155538&action=edit
CLI atr tvf warning
SUMMARY
***
kbackup tar archives cannot be restored - kbackup says the tar files are
corrupt, and running tar tvf in a shell on the files confirms this.
**
STEPS TO REPRODUCE
1. Set up kbackup with a profile and run a full backup, and set up
incremental backups as a cron job every 2 days
2. Attempt to restore a part of a backup of .config info in home directory
3.
OBSERVED RESULT
Choosing an archive to restore almost always fails with a message :-
"The archive you're trying to open is corrupt.
Some files may be missing or damaged.:
kbackup then asks if I want to open the archive Read-Only, and if I do, I see
that the recorded size of the archives is MUCH smaller than the tar file on the
drive - 3.6GB as opposed to 710GB. See the attached screenshots
EXPECTED RESULT
Restore should happen as desired.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 5.15.0-58-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 47.0 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: ASUS
ADDITIONAL INFORMATION
This is a catastrophic problem...it makes kbackup worse than useless. It also
let me down when I really need to restore a backup.
More Info about the details.....
1. The backups are on a home network NAS unit which is mounted via NFS - This
may be an issue!
2. The backups contain some very large binary files :- ISOs of various OSs and
many VirtualBox .vdi file for guest machines. These .vdi files are hundreds of
GB in size. Running tar tvf on these almost always fails on a large binary
file.
3. Running the backups (incremental or full) spends a lot of time on these .vdi
files, and it appears as if the kbackup GUI is frozen. However, the backup
completes with no errors after many hours.
This all makes kbackup almost useless, and because it doesn't report any
problems, or do any checking on the tar files, a user is left with a false
sense of security. I think kbackup needs to check (checksum or other
signature?) on the tar files, and perhaps to warn of an NFS mount, where tar
may fail.
--
You are receiving this mail because:
You are watching all bug changes.
