MySQL Forums
Forum List  »  InnoDB

InnoDB: Trying to access page number which is outside the tablespace bounds
Posted by: Aidan Diffey
Date: December 14, 2017 06:24AM


We are using MySQL 5.7.18 and we have hit an issue.

We have been storing data into the database successfully when a crash happened and we saw the following in our log file:

[ERROR] /usr/sbin/mysqld: The table '' is full
InnoDB: Assertion failure in thread 3397184320 in file line 1697
InnoDB: Failing assertion: offset > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
00:59:13 UTC - mysqld got signal 6 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 794067 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

When the server restart we then see:

[ERROR] InnoDB: Trying to access page number 323040 in space 1039, space name <> which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.

The file that the error is referring to is only 5.2G in size.

Any advice?

Options: ReplyQuote

Written By
InnoDB: Trying to access page number which is outside the tablespace bounds
December 14, 2017 06:24AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.