Bug #60006
closed
flooding of MySQL-Log
0%
Description
Version 6.2.3 is flooding the sql-log with this Error (11GB in max 5 min. !!!):
140630 22:06:00 InnoDB: Error: trying to access tablespace 574324073 page no. 976826416, InnoDB: but the tablespace does not exist or is just being dropped. 140630 22:06:00 InnoDB: Error: trying to access tablespace 574324073 page no. 976826416, InnoDB: but the tablespace does not exist or is just being dropped.
I don't know where it's coming from.
I just called the Install-tool and instead showing the content, the page is busy till my hdd-partition is full.
Common usage (page-creation, etc.) flooded the log-file yesterday too till nothing worked anymore but I've no editor that accepts large files like that, so I couldn't look up and I deleted the file.
Operating System: Windows Vista
Updated by Markus Klein almost 10 years ago
- Status changed from New to Rejected
This is NOT a TYPO3 error at all, but your database seems to be corrupted.
Try to repair the tables.
Updated by David Bruchmann almost 10 years ago
Thanks the hint about the database was helpful.
I changed nn my.ini the line
innodb_data_file_path = ibdata1:200M;
to
innodb_data_file_path = ibdata1:200M;ibdata2:200M
Like this another table-space for innodb-tables was automatically created and I have enough space for a few more installations. Take into account that the harddisk has to be large enough.
Detailed description about this issue in the mysql-manual:
http://dev.mysql.com/doc/refman/5.1/en/innodb-data-log-reconfiguration.html