[clug] Fedora 11 problem: mysql

[Eyal Lebedinsky]

I ran myisamchk on all the tables (*.MYI) and it reported errors only in user.MYI
	Checking MyISAM file: host.MYI
	Data records:       0   Deleted blocks:       0
	- check file-size
	- check record delete-chain
	- check key delete-chain
	- check index reference
	- check data record references index: 1

	---------

	Checking MyISAM file: user.MYI
	Data records:       7   Deleted blocks:       0
	- check file-size
	- check record delete-chain
	- check key delete-chain
	- check index reference
	- check data record references index: 1
	- check record links
	myisamchk: error: Checksum for key:  1 doesn't match checksum for records
	MyISAM-table 'user.MYI' is corrupted
	Fix it using switch "-r" or "-o"

I did a recover (myisamchk -r) for this table (later against *all* the tables).

The server still does not come up, giving the same error.
	[ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'host'; try to repair it

Eyal

Daniel Pittman wrote:
> Eyal Lebedinsky <eyal at eyal.emu.id.au> writes:
> 
>> It is not a logical suggestion - the upgrade utility needs a running server
>> (which there isn't).  That's why I wrote 'or any other utility'.
> 
> http://dev.mysql.com/doc/refman/5.1/en/upgrading-from-previous-series.html
> 
>     Incompatible change: MySQL 5.1 implements support for a plugin API that
>     allows the loading and unloading of components at runtime, without
>     restarting the server. Section 22.2, “The MySQL Plugin Interface”. The
>     plugin API requires the mysql.plugin table. After upgrading from an older
>     version of MySQL, you should run the mysql_upgrade command to create this
>     table. See Section 4.4.8, “mysql_upgrade — Check Tables for MySQL
>     Upgrade”.
> 
> So, mysql_upgrade does fix that, but the other problem, a damaged table, seems
> to be more persistent.
> 
> myisamchk should be able to run without the server running and repair the host
> table, which should get you moving forward.  Which, you are right, I should
> have identified as the first bit of problem needing to be resolved.
> 
> Regards,
>         Daniel
> 
> Why mysql dumps the faults in that order, I don't know, but it sure isn't
> helpful. :)
> 
> Regards,
>         Daniel

-- 
Eyal Lebedinsky	(eyal at eyal.emu.id.au)