Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Buldbot tests upgrade and upgrade2 attempt to do the live upgrade from 5.1.49 to the current version. It does not work for 10.0 anymore (and for MySQL 5.1 => 5.6 too). Upgrade 5.1 => 5.5 works, 5.5 => 5.6 / 10.0 works, but the direct upgrade 5.1 => 5.6 does not, it complains about InnoDB auto-extending:
2013-08-08 18:47:25 8805 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 p
|
ages, max 0 (relevant if non-zero) pages!
|
2013-08-08 18:47:25 8805 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you sh
|
ould now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of
|
zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
|
2013-08-08 18:47:25 8805 [ERROR] Plugin 'InnoDB' init function returned error.
|
2013-08-08 18:47:25 8805 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
|
(The messages above are from MySQL 5.1 => 5.6 upgrade).
Since it's a general recommendation to go through releases consequently, it's probably not a code bug, and we need to change the test for 10.0 to do the upgrade from 5.5, if possible.
Examples of the failures:
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-x86/builds/2171
(upgrade, upgrade2)
Attachments
Issue Links
- relates to
-
MDEV-4786 merge 10.0-monty → 10.0
-
- Closed
-