hi,
i used innodb with mysql 4.0.13. After 3 month the database crashed:
InnoDB: Fatal error: cannot allocate 4294959832 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 17206775 bytes. Operating system errno: 8
InnoDB: Cannot continue operation!
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: We now intentionally generate a seg fault so that
InnoDB: on Linux we get a stack trace.
I was able to rescue my data. So I updatet to mysql 4.0.23, because i thought that it was an bug...
But now, I have an other problem. The database runs a view hours before it hangs up. I can restart mysql but the error repeats...
050124 13:28:44 InnoDB: Started
bin\mysqld-nt: ready for connections.
Version: '4.0.23-nt' socket: '' port: 3306 Source distribution
050124 14:57:08 InnoDB: Operating system error number 995 in a file operation.
InnoDB: See
http://dev.mysql.com/doc/mysql/en/InnoDB.html
InnoDB: for installation help.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
I cant find any information about this. Is it a bug? Can it depends on a wrong mysql configuration?...
Some information about the database
- about 20 databases with innodb tablespace
- larges table has about 100.000 entries
- ibdata size about 60 MByte
Maybe its a configuration problem. I used as base the mysql-medium configuration.
innodb_buffer_pool_size = 64M
innodb_additional_mem_pool_size = 2M
innodb_log_file_size = 16M
innodb_log_buffer_size = 16M
I hope there is somebody who knows about that problem.
Best regards
Holger Kreißl
--
http://www.kreissl.info