title: MySQL server crashes, InnoDB outside the tablespace bounds
body: <p>I have a C# application performing some database operations on a MySQL 5.7 server. Once the complete system hunp up and I had to hard-reset it. When it comes to a specific table read/write operation now the database server crashes. The windows log shows</p>
  
  <pre><code>InnoDB: Trying to access page number 286720 in space 29, 
  space name myInstance/myTable, which is outside the tablespace bounds.
  Byte offset 0, len 16384, i/o type read. 
  </code></pre>
  
  <p>I tried to use <code>mysqlcheck --repair</code> but it fails because <code>note     : The storage engine for the table doesn't support repair</code>.</p>
  
  <p>I've read some advices that say I should start MySQL in a recovery mode, so I added </p>
  
  <pre><code>[mysqld]
  innodb_force_recovery=4
  </code></pre>
  
  <p>to the <code>my.ini</code> config file whereupon I should be able to use <code>mysqldump</code> to export the affected database table. But unfortunatelly I am not.  </p>
  
  <pre><code>mysqldump: Error 2013: Lost connection to MySQL server 
  during query when dumping table `myTable` at row: 1246
  </code></pre>
  
  <hr>
  
  <p><strong>Edit:</strong></p>
  
  <p>I checked the error log again and found lots of entries saying</p>
  
  <pre><code>[ERROR] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: 
  The table 'myTable' is full
  </code></pre>
  
  <p>I'm running the server on a Windows 32bit OS with an NTFS formatted partition. The <code>myTable.ibd</code> file size is around 4.5 GB, checking <a href="http://dev.mysql.com/doc/refman/5.7/en/table-size-limit.html" rel="nofollow">C.10.3 Limits on Table Size</a> states a file size limit of "2TB (possibly larger)" for Win32 w/ NTFS.
  While checking the reasons for my error the only possible cause I found was a full InnoDB tablespace. The solution might be "Changing the Number or Size of InnoDB Redo Log Files" although the coherence is a bit vague to me. Nevertheless I increased the size of the Redo Log Files from 48M to 100M. But nothing changed. </p>
  
  <p>If I perform a SQL <code>select * from myTable order by Id desc</code> the server crashes instantly. Error log entry is exactly the same as above.</p>
  
  <p>I checked the chapter <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-resize-system-tablespace.html" rel="nofollow">15.7.1 Resizing the InnoDB System Tablespace</a> as well and found out that <code>innodb_data_file_path</code> is not explicitly specified.</p>
  
  <p>Any ideas what I can do now? Thanks a lot!</p>