MySQL Bugs: #27242: Cannot write to InnoDB tables.

Bug #27242	Cannot write to InnoDB tables.
Submitted:	17 Mar 2007 22:49	Modified:	4 Oct 2012 7:02
Reporter:	Kyle Gato	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.0.33	OS:	Linux (centOS 4.4 (64 Bit))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Basically I cannot read or write InnoDB tables.

070317 14:37:06  mysqld started
InnoDB: Error: log file /opt/lampp/var/mysql/ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 52428800 bytes!
070317 14:37:06 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.0.33'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/auctionhouse.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/auctionhouse.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_action.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_action.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_aura.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_aura.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_gifts.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_gifts.frm'
070317 14:37:11 [ERROR] /opt/lampp/sbin/mysqld: Incorrect information in file: './wow_rc/character_homebind.frm'

My Inno configuration is as follows:

# Comment the following if you are using InnoDB tables
# skip-innodb
innodb_data_home_dir = /opt/lampp/var/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /opt/lampp/var/mysql/
innodb_log_arch_dir = /opt/lampp/var/mysql/
innodb_table_locks = 1
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 200M
innodb_additional_mem_pool_size = 10M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 50M
innodb_log_buffer_size = 10M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

How to repeat:
It just started doing this randomly, no idea how to repeat.

Suggested fix:
Tryed many things, spent few hours googling and searching through sites/trying my own things.

Thank you for a problem report. Have you changed the size of InnoDB log files and then restarted server (note the first error message in your report)?

You mean in the my.cnf file correct? I did try changing that to a larger number. (was 10M)

From the error log:

Actual size = 5242880
Specified size = 52428800

One more zero at the end

What is your recommended fix?

I would also like to add this:

070317 11:55:28  InnoDB: Error: Write to file /opt/lampp/var/mysql/ib_logfile0 failed at offset 0 5005824.
InnoDB: 4096 bytes should have been written, only 3584 were written.
InnoDB: Operating system error number 22.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
070317 11:55:28InnoDB: Assertion failure in thread 3647617968 in file fil0fil.c line 4023
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be

Update: Fixed, i deleted the log files and made new ones.

Duplicate of Bug#13494