Error Data File /var/db/mysql/ibdata1 Is Of A Different Size
Contents |
MySQL 5.7.12 refusing to run due to innodb_system data file ‘/var/db/mysql/ibdata1' being too small 2016-05-18 Trond Endrestøl Leave a comment One of my MySQL innodb auto-extending data file ./ibdata1 is of a different size 640 pages 5.7.12 instances refused to start after upgrading to FreeBSD's MySQL
Fatal Error: Mysql.user Table Is Damaged. Please Run Mysql_upgrade.
port version 5.7.12_1, claiming: 2016-05-18T11:03:26.688719Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is could not open or create the system tablespace of a different size 4864 pages (rounded down to MB) than specified in the .cnf file: initial 8192 pages, max 0 (relevant if non-zero) innodb_data_file_path pages! "Googling" the error message led me to http://sharadchhetri.com/2014/11/29/upgrading-mysql-5-1-5-6-service-failed-start/. I added the following line to the [mysqld] section in /var/db/mysql/my.cnf: innodb_data_file_path = ibdata1:10M:autoextend At least MySQL is happy. From the error message I deduced that the current ibdata1 file has a length equal to 4864pages × 16KiB/page = 77824KiB
[error] Can't Open The Mysql.plugin Table
= 76MiB, while MySQL 5.7.12 expects this to be at least 8192pages × 16KiB/page = 131072KiB = 128MiB. The current length was confirmed by running ls -l /var/db/mysql/ibdata1: -rw-r----- 1 mysql mysql 79691776 18 mai 13:03 /var/db/mysql/ibdata1 In the long run it's better to retire the old /var/db/mysql/my.cnf in favour of the "new" /usr/local/etc/mysql/my.cnf. Post navigation Previous Postportupgrade uninstall error, broken pipeNext PostAssertion failure in BIND 9.10.4 Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Yet another technical oriented blog, more or less IPv4/IPv6You are using IPv4 from 91.108.73.253 May 2016 M T W T F S S « Apr Jun » 1 2345678 9101112131415 16171819202122 23242526272829 3031 Archives September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015
van Eeden (OCA) Email Updates: Status: Unsupported Impact on me: None Category:MySQL Package Repos and Docker Images Severity:S3 [error] unknown/unsupported storage engine: innodb (Non-critical) Version:5.6 OS:Linux (Ubuntu 14.04.1 (trusty)) Assigned to: Akhil Mohan fatal error: can't open and lock privilege tables: table 'mysql.user' doesn't exist View Add Comment Files Developer Edit Submission View Progress Log Contributions [10 Aug 2014 10:25] Daniël
Error 1045 (28000): Access Denied For User 'root'@'localhost' (using Password: Yes)
van Eeden Description: I tried to install mysql-community-server 5.6.20-1ubuntu14.04 on Ubuntu 14.04.1. ==================================================================== $ sudo apt-get install mysql-community-server Reading package lists... Done Building dependency tree Reading state http://ximalas.info/2016/05/18/mysql-5-7-12-refusing-to-run-due-to-innodb_system-data-file-vardbmysqlibdata1-being-too-small/ information... Done The following NEW packages will be installed: mysql-community-server 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 13.8 MB of archives. After this operation, 89.0 MB of additional disk space will be used. Get:1 http://repo.mysql.com/apt/ubuntu/ trusty/mysql-5.6 mysql-community-server amd64 5.6.20-1ubuntu14.04 [13.8 MB] Fetched 13.8 MB in 3s https://bugs.mysql.com/bug.php?id=73521 (4,261 kB/s) Preconfiguring packages ... Selecting previously unselected package mysql-community-server. (Reading database ... 461119 files and directories currently installed.) Preparing to unpack .../mysql-community-server_5.6.20-1ubuntu14.04_amd64.deb ... Unpacking mysql-community-server (5.6.20-1ubuntu14.04) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up mysql-community-server (5.6.20-1ubuntu14.04) ... 2014-08-10 12:05:13 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. 2014-08-10 12:05:13 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). dpkg: error processing package mysql-community-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: mysql-community-server E: Sub-process /usr/bin/dpkg returned an error code (1) ==================================================================== From the errorlog: ==================================================================== 2014-08-10 12:05:14 21208 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .c
space size" Error? Discussion When an InnoDB tablespace approaches its maximum size, it can be expanded by adding additional tablespace files. The last file in the list of tablespace http://www.mysqlab.net/knowledge/kb/detail/topic/innodb/id/5082 files can be set to autoextend, growing in size as the tablespace grows, up to a maximum configurable size. When the autoextend file reaches its maximum size, it can be converted http://grokbase.com/t/mysql/mysql/037yjm9hq8/innodb-data-file-of-different-size to a regular tablespace file and a new tablespace file can be added with the autoextend attribute. When adding tablespace files, if incorrect file size information is entered in the MySQL data file configuration file, the "wrong table space size" error can be encountered, producing an error like the one below: InnoDB: Error: data file .\\ibdata1 is of a different size InnoDB: 640 pages (rounded down to MB) InnoDB: than specified in the .cnf file 1280 pages! InnoDB: Could not open or create data files. InnoDB: If you tried to add new data files, and is of a it failed here, InnoDB: you should now edit innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove the new ibdata files InnoDB created InnoDB: in this failed attempt. InnoDB only wrote those files full of InnoDB: zeros, but did not yet use them in any way. But be careful: do not InnoDB: remove old data files which contain your precious data! Solution First, ensure that all static sized tablespace files are accurately represented in your configuration file. When adding tablespace files to a tablespace that has an autoextend tablespace file, follow these directions: If your last data file already was defined with the keyword autoextend, the procedure to edit my.cnf must take into account the size to which the last data file has grown. You have to look at the size of the data file, round the size downward to the closest multiple of 1024 * 1024 bytes (i.e., 1MB), and specify the rounded size explicitly in innodb_data_file_path. Then you can add another data file. Remember that only the last data file in the innodb_data_file_path can be specified as auto-extending. As an exam
22:04:22 mysqld startedInnoDB: Error: data file /usr/local/mysql/data/ibdata1 is of a different sizeInnoDB: 81024 pages (rounded down to MB)InnoDB: than specified in the .cnf file 16384 pages!InnoDB: Could not open data files030729 22:04:23 Can't init databases030729 22:04:23 Aborting030729 22:04:23 InnoDB: Warning: shutting down a not properly startedInnoDB: or created database!030729 22:04:23/usr/local/mysql-standard-4.0.13-sun-solaris2.8-sparc/bin/mysqld: ShutdownComplete030729 22:04:23 mysqld endedI am assuming I need to change values in the following line taken from my.cnffileinnodb_data_file_path = ibdata1:10M;ibdata2:10M:autoextendPlease helpThanks--Asif Iqbalhttp://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08There's no place like 127.0.0.1 reply Tweet Search Discussions Search All Groups mysql 4 responses Oldest Nested Paul DuBois Most likely you were running without any InnoDB-related options in your option file, so it was using its default values. Then you added the option shown above, which explicitly specifies sizes for the data files -- and which does not match the number or size of the default data file. What I'd do if it were me in your situation: - Remove the innodb_data_file_path line from your my.cnf file - Restart the server; it should come up normally now - Perform a complete dump of all your databases (just Paul DuBois at Jul 30, 2003 at 5:07 am ⇧ At 22:08 -0400 7/29/03, Asif Iqbal wrote:I just decided to use my.cnf and bumped into this error message030729 22:04:22 mysqld startedInnoDB: Error: data file /usr/local/mysql/data/ibdata1 is of a different sizeInnoDB: 81024 pages (rounded down to MB)InnoDB: than specified in the .cnf file 16384 pages!InnoDB: Could not open data files030729 22:04:23 Can't init databases030729 22:04:23 Aborting030729 22:04:23 InnoDB: Warning: shutting down a not properly startedInnoDB: or created database!030729 22:04:23/usr/local/mysql-standard-4.0.13-sun-solaris2.8-sparc/bin/mysqld: ShutdownComplete030729 22:04:23 mysqld endedI am assuming I need to change values in the following line taken from my.cnffileinnodb_data_file_path = ibdata1:10M;ibdata2:10M:autoextendPlease helpMost likely you were running without any InnoDB-related optionsin your option file, so it was using its default values. Thenyou added the option shown above, which explicitly specifiessizes for the data files -- and which does not match the numberor size of the default data file.What I'd do if it were me in your situation:- Remove the innodb_data_file_path line from your my.cnf file- Restart the server; it should come up normally now- Perform a complete dump of all your databases (j