A 2 GB row is written to a MyISAM table but reads back as a crashed table with error 127

# mysqld options required for replay:  --max_allowed_packet=1073741824

CREATE TABLE t1 (a LONGBLOB, b LONGBLOB) ENGINE=MyISAM;

INSERT INTO t1 VALUES (REPEAT('a',1073741824), REPEAT('b',1073741824));

SELECT LENGTH(a), LENGTH(b) FROM t1;

SET @save_max_allowed_packet= @@global.max_allowed_packet;

SET GLOBAL max_allowed_packet= 1073741824;

--connect (con1,localhost,root)

CREATE TABLE t1 (a LONGBLOB, b LONGBLOB) ENGINE=MyISAM;

INSERT INTO t1 VALUES (REPEAT('a',1073741824), REPEAT('b',1073741824));

--disable_result_log

--error 0,ER_CRASHED_ON_USAGE

SELECT LENGTH(a), LENGTH(b) FROM t1;

--enable_result_log

--let $err= $mysql_errno

DROP TABLE t1;

if ($err)

{

  --die The INSERT of a 2 GB row into the MyISAM table succeeded, but the table now reads as crashed

}

--disconnect con1

--connection default

SET GLOBAL max_allowed_packet= @save_max_allowed_packet;

mysqltest: At line 14: The INSERT of a 2 GB row into the MyISAM table succeeded, but the table now reads as crashed

ERROR 1194 (HY000) at line 4: Table 't1' is marked as crashed and should be repaired

2026-10-06 18:53:14 5 [ERROR] Got error 127 when reading table './test/t1'

2026-10-06 18:53:14 5 [ERROR] mariadbd: Table 't1' is marked as crashed and should be repaired

Table	Op	Msg_type	Msg_text

test.t1	repair	info	Wrong bytesec:  13-128-  0 at          0; Skipped

test.t1	repair	info	Found link that points at 7016996765293437281 (outside data file) at 83886068

test.t1	repair	info	Found link that points at 7016996765293437281 (outside data file) at 100663280

test.t1	repair	warning	Number of rows changed from 1 to 0

test.t1	repair	status	OK