[MDEV-27269] Bootstrap ignores failure to initialize storage engine Created: 2021-12-15  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Server, Tests
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Oleksandr Byelkin
Resolution: Unresolved Votes: 0
Labels: bootstrap

Issue Links:
Relates
relates to MDEV-27268 Failed InnoDB initialization leaves g... Closed

 Description   

MariaDB Server bootstrap will ignore the failure of InnoDB to initialize itself:

./mtr --mysqld=--innodb-read-only innodb.innodb

10.2 6b066ec33285c089ce770c2d1eb50bc49787ee92

innodb.innodb 'innodb'                   [ skipped ]  Test requires InnoDB with 16k Page size.
line
2021-12-15 13:06:01 140419257711680 [ERROR] InnoDB: Can't create file './ibdata1' when --innodb-read-only is set
2021-12-15 13:06:01 140419257711680 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1873] with error Generic error
2021-12-15 13:06:01 140419257711680 [ERROR] Plugin 'InnoDB' init function returned error.
2021-12-15 13:06:01 140419257711680 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
^ Found warnings in /dev/shm/10.2o/mysql-test/var/log/mysqld.1.err

I think that already the bootstrap should have failed.

Another (maybe more practical) way to reproduce the bootstrap failure is a too small innodb_log_file_size, as described in MDEV-27268.



 Comments   
Comment by Sergei Golubchik [ 2021-12-15 ]

you want mysqld to fail, you need to use --innodb=FORCE

Generated at Thu Feb 08 09:51:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.