[MDEV-15335] Trying to access update undo rec field N in index "CLUST_IND" of table "SYS_INDEXES" but index has only M fields Created: 2018-02-16  Updated: 2020-08-25  Resolved: 2018-06-28

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.1.28
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Claudio Nanni Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Ubuntu



 Description   

A 10.1.28 Slave of a 10.0.32 Master crashes with:

InnoDB: Error: trying to access update undo rec field 38 in index "CLUST_IND" of table "SYS_INDEXES"
InnoDB: but index has only 9 fields
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
InnoDB: Run also CHECK TABLE "SYS_INDEXES"
InnoDB: n_fields = 11, i = 0, ptr 0x7ef432c82c81
180125 19:20:11 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.1.28-MariaDB-1~jessie
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=120
max_threads=2050
thread_count=32
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4634132 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48400
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56240cd0e6ae]
/usr/sbin/mysqld(handle_fatal_signal+0x2fd)[0x56240c84492d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7efd03337890]
/usr/sbin/mysqld(+0x80eadc)[0x56240caa2adc]
/usr/sbin/mysqld(+0x7de42a)[0x56240ca7242a]
/usr/sbin/mysqld(+0x7a5373)[0x56240ca39373]
/usr/sbin/mysqld(+0x80b56a)[0x56240ca9f56a]
/usr/sbin/mysqld(+0x7fa7f4)[0x56240ca8e7f4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7efd03330064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7efd014da62d]

Both servers settings variables are available if needed.



 Comments   
Comment by Marko Mäkelä [ 2018-02-16 ]

claudio.nanni, does this case involve copying any files?
The other day, we discussed a support customer who apparently suffered from corruption caused by Mariabackup wrongly restoring an incremental backup.
This had been fixed as MDEV-13807 in a later version.

I would need the data directory, or alternatively a core dump with mysqld and all .so files in order to diagnose this.

Comment by Elena Stepanova [ 2018-06-28 ]

Closing for now since there is nothing to work with. Please feel free to comment if you get any additional information, and the issue will be re-opened.

Generated at Thu Feb 08 08:20:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.