[MDEV-33023] Crash in mariadb-backup --prepare --export after --prepare Created: 2023-12-14 Updated: 2024-02-08 Resolved: 2024-02-08 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Backup |
| Affects Version/s: | 10.5, 10.6 |
| Fix Version/s: | 10.5.25, 10.6.18 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Debarun Banerjee |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | not-10.8, regression | ||
| Description |
|
The following change to an existing regression test causes a crash:
The 10.4 branch does not crash. |
| Comments |
| Comment by Debarun Banerjee [ 2024-01-18 ] |
|
mariadb-backup with --prepare option could result in empty redo log The assert is already marked not applicable for server operation backup |
| Comment by Debarun Banerjee [ 2024-01-22 ] |
|
The previous fix was good for 10.6 but 10.5 has another issue. Issue-1: System tablespace object is not there in fil space hash i.e. srv_sys_space.open_or_create() is not called. Issue-2: The system tablespace data file ibdata1 is not opened i.e. fil_system.sys_space->open() is not called. |
| Comment by Debarun Banerjee [ 2024-01-23 ] |
|
commit 7c170595d38938de516bfa0a9b7266a3a0edf001 (HEAD Address review comments from marko. Modified server_start to open Updated https://github.com/MariaDB/server/pull/3009 The only possible impact is if there is any case where mariabackup works without the system tablespace ibdata1 |
| Comment by Marko Mäkelä [ 2024-01-24 ] |
|
The problem is caused by the fact that no ib_logfile0 would exist, and therefore the system and undo tablespaces would not be opened. In |
| Comment by Debarun Banerjee [ 2024-01-25 ] |
|
The patch is already reviewed in github. Please mark the review complete. |
| Comment by Debarun Banerjee [ 2024-02-08 ] |
|
Pushed to 10.5. commit fb9da7f7518bc310aff4eac215e046d63acded62 |