https://bugs.kde.org/show_bug.cgi?id=479206
--- Comment #3 from pallaswept <pallasw...@proton.me> --- (In reply to Martin Koller from comment #2) > Hi. Thanks for your report - jour style is fun to read :-) > > I tried to reproduce this issue here, but using a smaller file with ca. 65GB > and some other smaller files. > The backup completed here after more than 5(!) hours... > But the backup archive did correctly include all files, also the large one! > > Also checking the source and I can't see how a file would not be included in > the tar file without an error given. > > Just to be sure: How did you check the content of the archive after the > backup? > Does "tar -tvf <backup.tar>" also not show the large file? Hello again Martin and thanks once again for looking into this for me. I really didn't expect a quick reply at this time of year, I hope that I have not interrupted your celebrations, and that you are enjoying the festive season. I looked for the file using dolphin at first, and then I tried ark. It was a better idea to try it with tar, thanks for finding the right arguments for me, you saved this dummy from having to read the manpage :D Unfortunately, I don't see the file listed there, either. There's obviously something 'special' about my PC that is causing this, but I have no idea what it might be. The specifics of the operation are that might be unique are that I am running Kbackup with kdesu (so I get root access to files for backup), the file is stored on a BTRFS file system and has the C attribute set, in order to disable copy-on-write (which I read as a recommendation for VM images and databases), and I am backing up to an external USB 3.1 (aka 3.2 Gen2x1 - the 10GBps variety) NVMe hard drive. I might try a few experiments and see if I can get it to include the file, and that should give us a hint. I will try without compression, and try backing up to a different destination (the same internal NVMe disk - there is enough space, and a different USB-connected spinning-rust type drive), and try without kdesu (This file doesn't need root access), and try backing up only this file (rather than using the profile I am using presently).... Hopefully one or more of those will work, and give us a hint about why it failed. I will return with some more info after I do the experiments. -- You are receiving this mail because: You are watching all bug changes.
