Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.11.11
-
None
-
Mariadb server version 10.11.11 with Galera Cluster on three VMs.
Description
Hello, I installed a Mariadb environment version 10.11.11 with Galera Cluster on three VMs. For a few months I have randomly and intermittently errors of the type shown below or reports of corrupt indexes:
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 2025-03-05 5:30:53 77 [ERROR] InnoDB: ibuf cursor restoration fails! ibuf record inserted to page [page id: space=11080, page number=1920] in file ./moodleea/mdl_user_devices.ibd
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 2025-03-05 5:30:53 77 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: PHYSICAL RECORD: n_fields 7; 1-byte offsets; info bits 0
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 0: len 4; hex 00002b48; asc +H;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 1: len 1; hex 00; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 2: len 4; hex 00000780; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 3: len 22; hex 000100010c0f03fc80e0860800088000860800088000; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 4: len 30; hex 41453333393630332d443043352d343631332d383939362d393633353146; asc AE339603-D0C5-4613-8996-96351F; (total 36 bytes);
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 5: len 8; hex 80000000000035c5; asc 5 ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 6: len 8; hex 8000000000010e17; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: PHYSICAL RECORD: n_fields 7; 1-byte offsets; info bits 0
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 0: len 4; hex 00002b48; asc +H;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 1: len 1; hex 00; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 2: len 4; hex 00000780; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 3: len 22; hex 000100010c0f03fc80e0860800088000860800088000; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 4: len 30; hex 41453333393630332d443043352d343631332d383939362d393633353146; asc AE339603-D0C5-4613-8996-96351F; (total 36 bytes);
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 5: len 8; hex 80000000000035c5; asc 5 ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 6: len 8; hex 8000000000010e17; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: DATA TUPLE: 3 fields;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 0: len 4; hex 00002b48; asc +H;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 1: len 1; hex 00; asc ;;
Mar 5 05:30:53 moodlecldb01b mariadbd[35616]: 2: len 4; hex 00000780; asc ;;
Recreating the index with the optimize table command "table_name"; I can restore operation.
Do you have any suggestions for me?
Thanks
Carlo
Attachments
Issue Links
- relates to
-
MDEV-32132 DROP INDEX followed by CREATE INDEX may corrupt data
-
- Closed
-