description: There is a bug in gbak implementation of backup process with volumes.
According to Firebird implementation, it sgould be not possible to create volume of backup with explicitly specified size which is more than 4gb.
Bug is in the following behaviour - if there will be set size which more than 4Gb and reminder of its division by 4 is not 0, backup volume will be created with remainder's size.
Example:
gbak -b -user SYSDBA -pass masterkey database.fdb vol1.fbk 41g vol2.fbk

vol1.fbk will be 1Gb in size, and rest is in vol2.fbk.

What should be done:
1) Wrong behaviour should be fixed (probably backported?) so it should not be possible to specify more than 4Gb size
2) In the future version implement support of bigger volumes, because 4Gb is obviously outdated limitation.

=>

There is a bug in gbak implementation of backup process with volumes.
According to Firebird implementation, it should be not possible to create volume of backup with explicitly specified size which is more than 4gb.
Bug is in the following behaviour - if there will be set size which more than 4Gb and reminder of its division by 4 is not 0, backup volume will be created with remainder's size.
Example:
gbak -b -user SYSDBA -pass masterkey database.fdb vol1.fbk 41g vol2.fbk

vol1.fbk will be 1Gb in size, and rest is in vol2.fbk.

What should be done:
1) Wrong behaviour should be fixed (probably backported?) so it should not be possible to specify more than 4Gb size
2) In the future version implement support of bigger volumes, because 4Gb is obviously outdated limitation.

assignee: Alexander Peshkov [ alexpeshkoff ]

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

status: Resolved [ 5 ] => Closed [ 6 ]

QA Status: No test

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested