Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.3.32, 10.3.33, 10.3.34
-
Product version: Plesk Obsidian 18.0.42.1
OS version: CloudLinux 7.9 x86_64
Build date: 2022/03/14 17:00
Description
Version 10.3.32
2022-02-12 21:27:54 0x7ff3d8956700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.32/storage/innobase/btr/btr0cur.cc line 7699
Version 10.3.33
2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.33/storage/innobase/btr/btr0cur.cc line 7699
Version 10.3.34 (Error still there):
2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699
Attachments
Issue Links
- relates to
-
MDEV-13542 Crashing on a corrupted page is unhelpful
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Affects Version/s | 10.3.32 [ 26029 ] | |
Description |
*Version 10.3.33*
2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.34 (Error still there):* 2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699 |
*Version 10.2.32*
2022-02-12 21:27:54 0x7ff3d8956700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.32/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.33* 2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.33/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.34 (Error still there):* 2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699 |
Description |
*Version 10.2.32*
2022-02-12 21:27:54 0x7ff3d8956700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.32/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.33* 2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.33/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.34 (Error still there):* 2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699 |
*Version 10.3.32*
2022-02-12 21:27:54 0x7ff3d8956700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.32/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.33* 2022-03-18 00:04:16 0x7fca28acc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.33/storage/innobase/btr/btr0cur.cc line 7699 *Version 10.3.34 (Error still there):* 2022-03-24 17:08:49 0x7fed3c4ae700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 7699 |
Link |
This issue relates to |
Assignee | Marko Mäkelä [ marko ] | |
Status | Open [ 1 ] | Needs Feedback [ 10501 ] |
Status | Needs Feedback [ 10501 ] | Open [ 1 ] |
Fix Version/s | N/A [ 14700 ] | |
Resolution | Cannot Reproduce [ 5 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
The failing assertion is a consistency check in btr_check_blob_fil_page_type():
ut_a(space_id == page_get_space_id(page));
It suggests that a BLOB pointer in a clustered index record is pointing to an invalid page. There are various possible reasons for that, such as, an attempt to "fix" crash recovery failures by removing ib_logfile*, or an attempt to copy data files while the server is running, without using a tool like mariabackup.
I am not aware of any currently open BLOB bugs.