56,687
社区成员
发帖
与我相关
我的任务
分享MYSQL服務器掛了！！求分析引起此類錯誤的原因。附錯誤日誌
一周開始了，發現MYsql服務起不來了。打開它的錯誤日誌，發現如下內容。
求高手幫忙分析引起此類錯誤的原因，給一個解決方案。。。。 謝謝
120813 10:37:10 [Note] Plugin 'FEDERATED' is disabled.
120813 10:37:10 InnoDB: The InnoDB memory heap is disabled
120813 10:37:10 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120813 10:37:10 InnoDB: Compressed tables use zlib 1.2.3
120813 10:37:10 InnoDB: Initializing buffer pool, size = 200.0M
120813 10:37:11 InnoDB: Completed initialization of buffer pool
120813 10:37:11 InnoDB: Error: data file E:\mysql5521data\ibdata2 uses page size 524288,
120813 10:37:11 InnoDB: but the only supported page size in this release is=16384
120813 10:37:11 InnoDB: Could not open or create data files.
120813 10:37:11 InnoDB: If you tried to add new data files, and it failed here,
120813 10:37:11 InnoDB: you should now edit innodb_data_file_path in my.cnf back
120813 10:37:11 InnoDB: to what it was, and remove the new ibdata files InnoDB created
120813 10:37:11 InnoDB: in this failed attempt. InnoDB only wrote those files full of
120813 10:37:11 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
120813 10:37:11 InnoDB: remove old data files which contain your precious data!
120813 10:37:11 [ERROR] Plugin 'InnoDB' init function returned error.
120813 10:37:11 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120813 10:37:11 [ERROR] Unknown/unsupported storage engine: INNODB
120813 10:37:11 [ERROR] Aborting
配置文件里的相關內容：
innodb_data_home_dir = "E:\\mysql5521data\\"
innodb_data_file_path = ibdata1:10M;ibdata2:20M:autoextend
文件系統里的相關內容：
ibdata1 大小 10M
ibdata2 大小 20M
求高手幫忙分析引起此類錯誤的原因，給一個解決方案。。。。 謝謝
120813 10:37:10 [Note] Plugin 'FEDERATED' is disabled.
120813 10:37:10 InnoDB: The InnoDB memory heap is disabled
120813 10:37:10 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120813 10:37:10 InnoDB: Compressed tables use zlib 1.2.3
120813 10:37:10 InnoDB: Initializing buffer pool, size = 200.0M
120813 10:37:11 InnoDB: Completed initialization of buffer pool
120813 10:37:11 InnoDB: Error: data file E:\mysql5521data\ibdata2 uses page size 524288,
120813 10:37:11 InnoDB: but the only supported page size in this release is=16384
120813 10:37:11 InnoDB: Could not open or create data files.
120813 10:37:11 InnoDB: If you tried to add new data files, and it failed here,
120813 10:37:11 InnoDB: you should now edit innodb_data_file_path in my.cnf back
120813 10:37:11 InnoDB: to what it was, and remove the new ibdata files InnoDB created
120813 10:37:11 InnoDB: in this failed attempt. InnoDB only wrote those files full of
120813 10:37:11 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
120813 10:37:11 InnoDB: remove old data files which contain your precious data!
120813 10:37:11 [ERROR] Plugin 'InnoDB' init function returned error.
120813 10:37:11 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120813 10:37:11 [ERROR] Unknown/unsupported storage engine: INNODB
120813 10:37:11 [ERROR] Aborting
配置文件里的相關內容：
innodb_data_home_dir = "E:\\mysql5521data\\"
innodb_data_file_path = ibdata1:10M;ibdata2:20M:autoextend
文件系統里的相關內容：
ibdata1 大小 10M
ibdata2 大小 20M
...全文
请发表友善的回复…
发表回复
rucypli 2012-08-13
- 打赏
- 举报
Added to changelog for 5.5.22, 5.6.5:
After using an ALTER TABLE statement to change the KEY_BLOCK_SIZE
property for an InnoDB table, for example when switching from an
uncompressed to a compressed table, subsequent server restarts could
fail with a message like:
InnoDB: Error: data file path/ibdata2 uses page size 1024,
InnoDB: but the only supported page size in this release is=16384
After using an ALTER TABLE statement to change the KEY_BLOCK_SIZE
property for an InnoDB table, for example when switching from an
uncompressed to a compressed table, subsequent server restarts could
fail with a message like:
InnoDB: Error: data file path/ibdata2 uses page size 1024,
InnoDB: but the only supported page size in this release is=16384
rucypli 2012-08-13
- 打赏
- 举报
