Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.11, 11.4, 11.8, 12.3
-
None
Description
CREATE SEQUENCE s ENGINE=Aria TRANSACTIONAL=1; |
SELECT NEXTVAL(s); |
--let $shutdown_timeout= 0
|
--source include/restart_mysqld.inc
|
SELECT NEXTVAL(s); |
 |
DROP SEQUENCE s; |
|
10.11 14f96a2e08073e7fa4aee5b182ca0111380089ad |
# restart
|
SELECT NEXTVAL(s);
|
NEXTVAL(s)
|
1001
|
Warnings:
|
Error 145 Got error '145 "Table was marked as crashed and should be repaired"' for './test/s'
|
Warning 1034 1 client is using or hasn't closed the table properly
|
Note 1034 Table is fixed
|
DROP SEQUENCE s;
|
bug.t [ fail ] Found warnings/errors in server log file!
|
Test ended at 2026-03-06 18:47:28
|
line
|
2026-03-06 18:47:28 3 [ERROR] mariadbd: Got error '145 "Table was marked as crashed and should be repaired"' for './test/s'
|
2026-03-06 18:47:28 3 [Warning] Checking table: './test/s'
|
^ Found warnings in /share8t/bld/10.11-asan-ubsan/mysql-test/var/log/mysqld.1.err
|
There is no signs of Aria recovery upon server restart (no mariadbd: Aria engine: starting recovery ... which appears in the same situation for a regular Aria table.
Attachments
Issue Links
- relates to
-
MDEV-38997 Server crashes in MDL_context::upgrade_shared_lock when the underlying sequence is damaged
-
- Open
-