MySQL Bugs: #119554: CRASH SERVER after Truncate

Bug #119554	CRASH SERVER after Truncate
Submitted:	15 Dec 2025 16:22	Modified:	29 Dec 2025 14:36
Reporter:	Alexis Amoudru	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	8.0.43	OS:	CentOS ( 7.9.2009 (Core))
Assigned to:		CPU Architecture:	Any

Description:
CREATE TABLE `test_steph` (   `cp1` int DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
insert into test_steph values (22);
select * from test_steph;
commit;
truncate test_steph;
Query OK, 0 rows affected (0.02 sec)

we restart server try to trucate same table and we get crashed server .
truncate test_steph;
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/mysql/socket/mysql_testbase2.sock' (111)
ERROR:
Can't connect to the server

How to repeat:
we restart server try to trucate same table and we get crashed server .
truncate test_steph;

ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/mysql/socket/mysql_testbase2.sock' (111)
ERROR:
Can't connect to the server

Hello 

Do you know if its a problem well known ?

Regards
Alexis

Hello ,

can we get a feed back on this problem its becoming a major problem for us !!!

thank you 

Alexis

Same testcase on a new 8.0.43 didn't have the problem.

Please upload the mysql error log so we can see if your server crashed during startup.

hi ,

send you the errorlog if you can tell me the cause ??

thanks
Alexis

The assertion is:
[ERROR] [MY-013183] [InnoDB] Assertion failure: ha_innodb.cc:11474:strlen(m_remote_path) != 0 

which looks same as 
https://bugs.mysql.com/bug.php?id=117660

Which wasn't repeatable.  Can we also see my.cnf if you attach it privately?

And also which filesystem is used for the datadir?

I've found this is a duplicate of a an *internal* verified bug.
For your reference:

https://bugs.mysql.com/bug.php?id=117210
Bug 38169053

Apparently it's due to using symlinks for the directories.
So you can check on that.

Hello,

So i see your advices but since you change the website we cannot download the files and we cannot look at the bug you reference 117210 ?

for filesystem :
[root@mmysql ~]# df -T
Filesystem                 Type      1K-blocks       Used Available Use% Mounted                                                                                                                                                              on
devtmpfs                   devtmpfs       4096          0      4096   0% /dev
tmpfs                      tmpfs     264127532          4 264127528   1% /dev/sh                                                                                                                                                             m
tmpfs                      tmpfs     105651016      47500 105603516   1% /run
/dev/mapper/vgs-root       ext4      102626232    8498984  88867984   9% /
/dev/sdb2                  ext4        1992552     267588   1603724  15% /boot
/dev/mapper/vgs-home       ext4      182586848    4648844 168590320   3% /home
/dev/mapper/vgs-var        ext4       61611820     889600  57560108   2% /var
/dev/mapper/vg_vol1-myvol1 ext4      308524224  239986652  52808932  82% /myvol1
/dev/mapper/vg_vol1-myvol2 ext4      659439544  537484200  88400912  86% /myvol2
/dev/mapper/vg_vol1-myvol3 ext4     1716330420 1456772552 172316552  90% /myvol3
tmpfs                      tmpfs      52825504          4  52825500   1% /run/us                                                                                                                                                             er/1002

 i send you my.cnf after .
Regards 
Alexis

hi ,
i put my.cnf

regards Alex

HEllo,

I sent you all informations you asked me  but i dont have feedback since this time !!

Can you tell me what i should do to escape this bug and solve this problem ?

Regards
Alexis

Apparently the bug is exposed when you use symlinks for the data directory.  So if that's the case here too,  don't use symlinks.

Hello dear ,

We dont think it's  due to symlinks because in Mysql  8.0.37 it was working fine .
WE tried  all version 8.0.4X and we get the bug with truncate after reboot , we downgrade to 8.0.37 and no more bugs .

Also when we create a table innodb  with explicit data directory we dont have the bug .

thks 
Regards
Alexis