[MDEV-5547] Bad error message when moving very old .frm files to MariaDB 5.5 Created: 2014-01-22  Updated: 2014-01-29  Resolved: 2014-01-22

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.34
Fix Version/s: 5.5.35

Type: Bug Priority: Major
Reporter: Michael Widenius Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None


 Description   

Copying host.frm from and old system to MariaDB gave the following error one access, check or repair:

Incorrect key file for table 'host'; try to repair it

This error doesn't tell what is wrong or how to fix it.



 Comments   
Comment by Michael Widenius [ 2014-01-22 ]

I have fixed this by adding a new handler error message when the .frm and storage engine definition differs:

Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine. You have to dump and restore the table to fix this

In addition I fixed that REPAIR TABLE .. USE_FRM will fix old tables with same storage format between versions (no VARCHAR fields).

Comment by Michael Widenius [ 2014-01-22 ]

In addition mysql_upgrade doesn't provide any usable error message if used with a not privileged user:

./client/mysql_upgrade --upgrade-system-tables --user=xxx
The --upgrade-system-tables option was used, databases won't be touched.
FATAL ERROR: Upgrade failed

Comment by Michael Widenius [ 2014-01-22 ]

After my changes it now looks like this:

./client/mysql_upgrade --upgrade-system-tables --user=test --password=test --silent
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 1044 (42000): Access denied for user 'test'@'localhost' to database 'mysql'
FATAL ERROR: Upgrade failed

Comment by Michael Widenius [ 2014-01-22 ]

All issues fixed and pushed into 5.5

Comment by Daniel Bartholomew [ 2014-01-29 ]

http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/4019

http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/4014

Generated at Thu Feb 08 07:05:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.