https://bugs.kde.org/show_bug.cgi?id=464712
Martin Koller <kol...@aon.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |ASSIGNED
--- Comment #3 from Martin Koller <kol...@aon.at> ---
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 12288000000
bytes,
which should be encoded as the string "133433000000", but KTar writes it as
"13343300000" leading to a size showing as 1536000000 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.
