| Bug #67979 | Error: data file /var/lib/mysql/ibdata2 uses page size 2048 | ||
|---|---|---|---|
| Submitted: | 27 Dec 2012 7:21 | Modified: | 2 Jan 2013 9:52 |
| Reporter: | rajnish kumar | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.5.20 | OS: | Linux (Red Hat Enterprise Linux Server release 6.0 (Santiago)) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | page size error | ||
[27 Dec 2012 10:32]
MySQL Verification Team
Hello Rajnish, Thank you for the bug report, duplicate of http://bugs.mysql.com/bug.php?id=64160 I would suggest you to use latest GA when upgrading.
[27 Dec 2012 13:03]
rajnish kumar
Hi Team, As a bug you can say that we have to upgrade it ,but you also know on live server we cant update our mysql server version on every release of mysql versions. I am not using any compression with block size 8. how my running database trows these error after running successful 5 months. if this error comes at upgrade time I understand but I mentioned all my cases what happens with my server ,Please read carefully and then reply or close it .
[27 Dec 2012 14:52]
MySQL Verification Team
Please test with latest released version how it was recommend if you continue to get same issue please re-open this bug report. Thanks.
[2 Jan 2013 7:18]
rajnish kumar
Hi All, Thanks For your valuable suggestion, I am going to upgrade my Db Server version. One thing I want to share with all of you ,I did some testing on this issue on my test machine and i Found some interesting things. Error : 130102 12:34:16 InnoDB: Error: data file ./ibdata2 uses page size 1024, 130102 12:34:16 InnoDB: but the only supported page size in this release is=16384 the issue occur when i just changed innodb_log_buffer_size from 64M to 128 M and I restart the mysql Db server , then I found my Mysql server is not started and when i viewed error log I found 130102 12:34:16 InnoDB: Error: data file ./ibdata2 uses page size 1024, 130102 12:34:16 InnoDB: but the only supported page size in this release is=16384 When I again rolled backed my innodb_log_buffer_size from 128M to 64M ,but still the same error occurs . Also I want to know which mysql version I used so that this type of error I didn't face in future. I also want to know which version of mysql have solution of this problem.
[2 Jan 2013 7:28]
MySQL Verification Team
The problem was introduced in 5.5.20 and as per the change log details documented in the below manual page, issue was fixed in 5.5.22 http://dev.mysql.com/doc/refman/5.5/en/news-5-5-22.html As a side note I would suggest you to use latest GA when upgrading.
[2 Jan 2013 9:52]
rajnish kumar
Hi Umesh, Thanks For providing me the details . Yes i Try the same thing on latest version 5.5.29 and I am happy to see these issue doesnot exist on new release. thanks for reply and provide me a lots of information.
Description: Hi All, I was running MySQL DB server of version 5.0.19 with master -slave replication on Linux (Red Hat Enterprise Linux Server release 6.0 (Santiago)) both machine have 16 gb ram, 6 months before (On July) I updated MySQL version to 5.5.20 on both server and now configured master - master replication in it . setup details m1 <-----> m2 | ----> m3 (slave of m1) (m1 is active for Application , means all ddl, dml comes on m1). m3 is slave of m1 , and m1 and m2 configured as master master Every thin is working fine ,now sudden on day replication is stop responding(on m2) ,time gap increasing and increasing on m2 server , I wait for 1 hour but still time gap increasing ,so I stop replication on m2 and start it after 2 seconds ,but still same issue occur , later I Restart(MySQL server) on m2 machine .now it stop successful but it does not start , when i view error log of m2 server ,it show below Error: 121226 2:33:31 [Note] /usr/sbin/mysqld: Shutdown complete 121226 02:33:31 mysqld_safe mysqld from pid file /var/lib/mysql//vta-161.pid ended 121226 02:33:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/ 121226 2:33:33 [Warning] option 'thread_cache_size': unsigned value 33554432 adjusted to 16384 121226 2:33:33 [Warning] option 'net_buffer_length': unsigned value 2097152 adjusted to 1048576 121226 2:33:33 [Note] Plugin 'FEDERATED' is disabled. 121226 2:33:33 InnoDB: The InnoDB memory heap is disabled 121226 2:33:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121226 2:33:33 InnoDB: Compressed tables use zlib 1.2.3 121226 2:33:33 InnoDB: Using Linux native AIO 121226 2:33:33 InnoDB: Initializing buffer pool, size = 4.0G 121226 2:33:33 InnoDB: Completed initialization of buffer pool 121226 2:33:34 InnoDB: Error: data file /var/lib/mysql/ibdata2 uses page size 2048, 121226 2:33:34 InnoDB: but the only supported page size in this release is=16384 121226 2:33:34 InnoDB: Could not open or create data files. 121226 2:33:34 InnoDB: If you tried to add new data files, and it failed here, 121226 2:33:34 InnoDB: you should now edit innodb_data_file_path in my.cnf back 121226 2:33:34 InnoDB: to what it was, and remove the new ibdata files InnoDB created 121226 2:33:34 InnoDB: in this failed attempt. InnoDB only wrote those files full of 121226 2:33:34 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 121226 2:33:34 InnoDB: remove old data files which contain your precious data! 121226 2:33:34 [ERROR] Plugin 'InnoDB' init function returned error. 121226 2:33:34 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 121226 2:33:34 [ERROR] Unknown/unsupported storage engine: InnoDB 121226 2:33:34 [ERROR] Aborting on All server, same linux OS version installed, same DB version . below is my.cnf of m2 server # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket=/tmp/mysql.sock # The MySQL server [mysqld] skip-host-cache skip-name-resolve datadir=/var/lib/mysql/ socket=/tmp/mysql.sock default-storage-engine=InnoDB port = 3306 socket = /tmp/mysql.sock key_buffer = 256M table_cache = 9000 max_heap_table_size=32M open_files_limit=318 max_allowed_packet = 64M sort_buffer_size = 256M read_buffer_size = 256M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 16M thread_cache_size = 32M query_cache_min_res_unit= 2K query_cache_type = 1 query_cache_size = 1024M query_cache_limit = 128M bulk_insert_buffer_size=20M join_buffer_size=128M #net_buffer_length=1M net_buffer_length=2M preload_buffer_size=1M binlog_cache_size=2M max_connections=1024 ## Logs ## # replication settings for primary database binlog_format=mixed log-bin=/var/lib/MySQLLogs/MySQLBinLog161 log-bin-index = /var/lib/MySQLLogs/BinLog161.index replicate-same-server-id = 0 log-slave-updates = 1 auto-increment-increment = 2 auto-increment-offset = 1 binlog-ignore-db=mysql relay-log-index = /var/lib/MySQLLogs/slave-relay161-bin.index relay-log = /var/lib/MySQLLogs/slave-relay161-bin log-error=/var/lib/MySQLLogs/MysqlError161.log slow-query-log = 1 long_query_time = 3 slow-query-log-file = /var/lib/MySQLLogs/MySQLSlowQuery161.log expire_logs_days=30 server-id = 2 innodb_file_per_table innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:500M;ibdata2:500M:autoextend innodb_autoextend_increment=50 innodb_log_group_home_dir = /var/lib/mysql/ innodb_buffer_pool_size = 4096M innodb_additional_mem_pool_size = 256M innodb_log_file_size = 64M innodb_log_buffer_size = 256M innodb_log_files_in_group=2 innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 innodb_fast_shutdown = 0 [mysqld_safe] log-error=/var/lib/MySQLLogs/MysqlError161.log pid-file=/var/run/mysqld/mysqld.pid i didn't understand why this error occur . Please suggest on the problem. In Error log I didn't find any error which is relevant to replication . How to repeat: I searched this problem on internet , no one providing me the solution, can you please suggest what to do to resolve the problem. I also want to know In which condition these type of error comes . In Error log I didn't find any error which is relevant to replication .