Share

KBackup

Tracker: Bugs

5 2GB limitation - ID: 516932
Last Update: Comment added ( frascone )

Using KBackup version 1.2.9 (on RedHat 7.1) and 1.2.11
on a vanilla 2.4.17 linux for a 4GB backup (using afio)
it always finishes prematurely at 2047 MBytes.
Also the "backup size" function doesn't work (empty
string).
My first suspicion: maybe a tape length limit is still
applied when FILE is choosen as backup medium:
Looking into the scripts, I found:
maxarchivelength=`expr $tapelength -
$bytes_written`
but I can't find the location where the tapelength
variable gets a value assigned.
a "grep tapelength * " only shows:
kbackup: maxarchivelength=`expr $tapelength -
$bytes_written`
Q: Where gets this 'tapelength' variable it's value?

Any suggestion?


Nobody/Anonymous ( nobody ) - 2002-02-13 12:29

5

Closed

None

Nobody/Anonymous

None

None

Public


Comments ( 3 )




Date: 2004-03-18 05:11
Sender: frasconeProject Admin

Logged In: YES
user_id=78392

Just checked in a fix supplied by rbonte (cvs only)


Date: 2004-03-17 02:37
Sender: rbonte

Logged In: YES
user_id=999757

This is a real bug in multibuf, because it is not compiled for large file

access. I submitted a patch to fix this, but I'm not sure whether this
works on all architectures (I'm on linux 2.4 where it works), as this is
architecture-dependent. 64 bit systems have no problem with this
limitation.

ldrolez, please check your facts, before you say that this is not a
problem. Remember that other users might base an important decision
on your comments.



Date: 2002-09-03 18:56
Sender: ldrolezAccepting Donations

Logged In: YES
user_id=49118

This is not a kbackup problem : It's a linux filesystem issue.
ext2 has a 2GB limit. xfs, jfs and reiserfs have much higher
limits.


Log in to comment.

Attached File

No Files Currently Attached

Changes ( 2 )

Field Old Value Date By
status_id Open 2004-03-18 05:11 frascone
close_date - 2004-03-18 05:11 frascone