Error: log file .\ib_logfile0 is of different size 0 56623104 bytes

SQL code

120827 14:08:19 [Note] Plugin 'FEDERATED' is disabled.120827 14:08:19 InnoDB: The InnoDB memory heap is disabled120827 14:08:19 InnoDB: Mutexes and rw_locks use Windows interlocked functions120827 14:08:19 InnoDB: Compressed tables use zlib 1.2.3120827 14:08:19 InnoDB: Initializing buffer pool, size = 4.0G120827 14:08:20 InnoDB: Completed initialization of buffer poolInnoDB: Error: log file .\ib_logfile0 is of different size 0 56623104 bytesInnoDB: than specified in the .cnf file 0 268435456 bytes!120827 14:08:20 [ERROR] Plugin 'InnoDB' init function returned error.120827 14:08:20 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.120827 14:08:20 [ERROR] Unknown/unsupported storage engine: INNODB120827 14:08:20 [ERROR] Aborting120827 14:08:20 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

我的my.ini配置如下，我的电脑是64bit win7

SQL code

#*** INNODB Specific options ***# Use this option if you have a MySQL server with InnoDB support enabled# but you do not plan to use it. This will save memory and disk space# and speed up some things.#skip-innodb# Additional memory pool that is used by InnoDB to store metadata# information.  If InnoDB requires more memory for this purpose it will# start to allocate it from the OS.  As this is fast enough on most# recent operating systems, you normally do not need to change this# value. SHOW INNODB STATUS will display the current amount used.innodb_additional_mem_pool_size=20M# If set to 1, InnoDB will flush (fsync) the transaction logs to the# disk at each commit, which offers full ACID behavior. If you are# willing to compromise this safety, and you are running small# transactions, you may set this to 0 or 2 to reduce disk I/O to the# logs. Value 0 means that the log is only written to the log file and# the log file flushed to disk approximately once per second. Value 2# means the log is written to the log file at each commit, but the log# file is only flushed to disk approximately once per second.innodb_flush_log_at_trx_commit=2# The size of the buffer InnoDB uses for buffering log data. As soon as# it is full, InnoDB will have to flush it to disk. As it is flushed# once per second anyway, it does not make sense to have it very large# (even with long transactions).innodb_log_buffer_size=4M# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and# row data. The bigger you set this the less disk I/O is needed to# access data in tables. On a dedicated database server you may set this# parameter up to 80% of the machine physical memory size. Do not set it# too large, though, because competition of the physical memory may# cause paging in the operating system.  Note that on 32bit systems you# might be limited to 2-3.5G of user level memory per process, so do not# set it too high.# memlockinnodb_buffer_pool_size=4G# Size of each log file in a log group. You should set the combined size# of log files to about 25%-100% of your buffer pool size to avoid# unneeded buffer pool flush activity on log file overwrite. However,# note that a larger logfile size will increase the time needed for the# recovery process.innodb_log_file_size=256M# innodb_log_files_in_group = 2# Number of threads allowed inside the InnoDB kernel. The optimal value# depends highly on the application, hardware as well as the OS# scheduler properties. A too high value may lead to thread thrashing.innodb_thread_concurrency=10innodb_lock_wait_timeout=500

[解决办法]
请先说明你是什么原因出现这个问题的
------解决方案--------------------

修改肯定要报错，因为修改必须删除原有的ib_logfile


搜一下整个硬盘看看