https://bugs.kde.org/show_bug.cgi?id=518106
Bug ID: 518106
Summary: Can't restore backups saved to an NTFS destination
using the button
Classification: Applications
Product: kup
Version First 0.10.0
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Attempting to restore a backup from the "Open and restore from existing
backups" button fails when the backup is stored in an NTFS file system. The
"Show files" button from the Backup Status tray icon also fails similarly.
STEPS TO REPRODUCE
1. Create a Kup backup plan with versioned backup with its destination at a
filesystem path that leads to an NTFS partition
2. Save a backup
3. Attempt to open the archive folder
OBSERVED RESULT
An error popup appears as described above. The message is "The backup archive
‘(path to my archive)’ could not be opened. Check if the backups really are
located there."
EXPECTED RESULT
It to open the interface to view and restore from the backup.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060 Ti
ADDITIONAL INFORMATION
When starting to use Kup, I created a backup from my home folder on a BTRFS
atop an nvme ssd to my Sata HDD that I carried over from my prior Windows
install. Since it has extra data on it from that install, it has an NTFS
filesystem on it. Bup itself has no problem inspecting and even mounting the
backup archive via `bup fuse`, but the Kup button does not work. I haven't
tried actually recovering from the backup, but I suspect it would work if `bup
fuse` does.
I told Kup to create recovery information and to verify integrity of backups in
the backup plan.
I've tested and verified that making a backup using the same settings except
that the destination is inside the BTRFS filesystem doesn't have this issue, so
I suspect it's that I'm crossing into NTFS.
--
You are receiving this mail because:
You are watching all bug changes.
