[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-02-04 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=464712

Martin Koller  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/util
   ||ities/kbackup/commit/92b35c
   ||f7f4fed327d68bfc1608878f872
   ||3a679a9
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Martin Koller  ---
Git commit 92b35cf7f4fed327d68bfc1608878f8723a679a9 by Martin Koller.
Committed on 04/02/2023 at 23:02.
Pushed by mkoller into branch 'master'.

Switch from KTar to libarchive to allow archival of files > ca. 8GB

M  +118  -98   src/Archiver.cxx
M  +21   -23   src/Archiver.hxx
M  +3-0src/CMakeLists.txt

https://invent.kde.org/utilities/kbackup/commit/92b35cf7f4fed327d68bfc1608878f8723a679a9

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-30 Thread Paul Hands
https://bugs.kde.org/show_bug.cgi?id=464712

--- Comment #6 from Paul Hands  ---
OK...I'll stop bothering you :-)  I'm just trying to get a working backup
solution that works well in KDE.  LibArchive sounds like the right call.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-30 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=464712

--- Comment #5 from Martin Koller  ---
I don't want to go that route. It would also need double the space on your disk
and is probably slow.
I looked into the ark sources since I can open a tar file with 12GB when I
created it on the command line.
What I found is that they are not using KTar but the libArchive library, which
can handle a lot of other archive formats as well
(which I don't need in kbackup).
It seems the simplest way is to also use this lib instead reimplemeting all
this enhanced tar formats libarchive
has already implemented.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-30 Thread Paul Hands
https://bugs.kde.org/show_bug.cgi?id=464712

--- Comment #4 from Paul Hands  ---
A thought.

It's possible to use the "split" command to break a large file into pieces. 
That might be an option inside KBackup, instead of making changes to
KTarespecially if you're not the maintainer.  It could be that this a new
option for KBackup - split files over a given size into chunks anyway?

There would be a bit of extra work at restore time to reassemble the pieces
(xaa, xab, xac...and so on) from the split operation...but KBackup doesn't do
restore, so perhaps some scripting for Ark?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-25 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=464712

Martin Koller  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #3 from Martin Koller  ---
Found the problem.
It's a bug in the KTar implementation.
The size of a file is stored inside the tar file header as an octal encoded
string.
strange, but obviously a very old format from the good old Unix days ;-) 

The string is limited to 11 chars, which means: the maximum file size is
8589934591 Bytes.
Sadly KTar has no check for an overflow in our case and simply cuts the 12th
character. In my testcase I have a file being ~12GB, which is 1228800
bytes,
which should be encoded as the string "13343300", but KTar writes it as
"1334330" leading to a size showing as 153600 bytes.

In the short term this means I need to implement a check which limits the
backup
to files with the above max length and kbackup will cancel a backup when a too
large
file is found.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-23 Thread Paul Hands
https://bugs.kde.org/show_bug.cgi?id=464712

--- Comment #2 from Paul Hands  ---
I'm available for testing and can create screen capture videos as needed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kbackup] [Bug 464712] KBackup archives cannot be restored. - tar files are corrupt

2023-01-23 Thread Paul Hands
https://bugs.kde.org/show_bug.cgi?id=464712

--- Comment #1 from Paul Hands  ---
Created attachment 155539
  --> https://bugs.kde.org/attachment.cgi?id=155539=edit
kbacup corruption message

-- 
You are receiving this mail because:
You are watching all bug changes.