Provide ability to specify extra-long name of log when doing gbak to avoid "attempt to store 256 bytes in a clumplet" message [CORE4398]

[firebird-automations]

Submitted by: @pavel-zotov

Votes: 1

Currently the following command:

/opt/fb25/bin/gbak -se localhost/3253:service_mgr -v -y /var/db/fb25/A012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.log -b /var/db/fb25/tmp25.fdb /var/db/fb25/tmp25.fbk

- shows:

gbak: ERROR:Internal error when using clumplet API: attempt to store 256 bytes in a clumplet with maximum size 255 bytes gbak:Exiting before completion due to errors

It is rarely need to specify such long name of log, may be it can occur if we have too deep folders tree with long names of each sub-folder. But anyway it will be useful to increase current limit.

Commits: FirebirdSQL/firebird@9e3f5a9a563a5822c7d47804db1f336503ee67ba FirebirdSQL/fbt-repository@661a3a51b79e5890ab5c8d44633a2f36a59c3d1e

[firebird-automations]

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov \[ alexpeshkoff \]

[firebird-automations]

Commented by: @AlexPeshkoff

Did you try in trunk?

[firebird-automations]

Commented by: @pavel-zotov

Yes, the same error message on LI-T3.0.0.31071.

[firebird-automations]

Commented by: @AlexPeshkoff

Use modern form of ClumpletWriter ctor in utilities.

[firebird-automations]

Modified by: @AlexPeshkoff

status: Open \[ 1 \] =\> Resolved \[ 5 \] resolution: Fixed \[ 1 \] Fix Version: 3\.0 Beta 1 \[ 10332 \]

[firebird-automations]

Modified by: @pavel-zotov

status: Resolved \[ 5 \] =\> Resolved \[ 5 \] QA Status: Done successfully

[firebird-automations]

Modified by: @pavel-zotov

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