Provide ability to specify extra-long name of log when doing gbak to avoid "attempt to store 256 bytes in a clumplet" message [CORE4398] #4720
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff Did you try in trunk? |
|
Commented by: @pavel-zotov Yes, the same error message on LI-T3.0.0.31071. |
|
Commented by: @AlexPeshkoff Use modern form of ClumpletWriter ctor in utilities. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Beta 1 [ 10332 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: 9e3f5a9 FirebirdSQL/fbt-repository@661a3a5
The text was updated successfully, but these errors were encountered: