Bug in mysqlcheck in Mysql-4.1

Hi,

Auto repair seems to not be launched when the table is marked as crashed.

How-to-repeat :

forum:/home/mysql/Hardwarefr# /usr/local/mysql/bin/mysqlcheck Hardwarefr
threadprive -uroot -p --auto-repair
Enter password:
Hardwarefr.threadprive
warning : Table is marked as crashed
warning : 17 clients is using or hasn't closed the table properly
error : Record-count is not ok; is 573207 Should be: 573217
warning : Found 17886 deleted blocks Should be: 17876
error : Corrupt
forum:/home/mysql/Hardwarefr#

(in fact the table has been marked as crash after a first launch of :

forum:/home/mysql/Hardwarefr#
/usr/local/mysql/bin/mysqlcheck -A -uroot -p --auto-repair

and then mysqlcheck failed with the following error message :

/usr/local/mysql/bin/mysqlcheck: Got error: 1103: Incorrect table name
'searchmainhardwarefr0.MYD' when executing 'REPAIR TABLE
`searchmainhardwarefr0.MYD`
(or something like that, unfortunately I'm not able to reproduce the bug
since mysqlcheck doesn't launch anymore the auto-repair because of the first
bug I described))

Regards,
Jocelyn


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12729@lists.mysql.com
To unsubscribe, e-mail

Bug in mysqlcheck in Mysql-4.1

joce writes:
> Hi,
>
> Auto repair seems to not be launched when the table is marked as crashed.
>
> How-to-repeat :
>
> forum:/home/mysql/Hardwarefr# /usr/local/mysql/bin/mysqlcheck Hardwarefr
> threadprive -uroot -p --auto-repair
> Enter password:
> Hardwarefr.threadprive
> warning : Table is marked as crashed
> warning : 17 clients is using or hasn't closed the table properly
> error : Record-count is not ok; is 573207 Should be: 573217
> warning : Found 17886 deleted blocks Should be: 17876
> error : Corrupt
> forum:/home/mysql/Hardwarefr#
>
> (in fact the table has been marked as crash after a first launch of :
>
> forum:/home/mysql/Hardwarefr#
> /usr/local/mysql/bin/mysqlcheck -A -uroot -p --auto-repair
>
> and then mysqlcheck failed with the following error message :
>
> /usr/local/mysql/bin/mysqlcheck: Got error: 1103: Incorrect table name
> 'searchmainhardwarefr0.MYD' when executing 'REPAIR TABLE
> `searchmainhardwarefr0.MYD`
> (or something like that, unfortunately I'm not able to reproduce the bug
> since mysqlcheck doesn't launch anymore the auto-repair because of the first
> bug I described))
>
> Regards,
> Jocelyn

Hi Jocelyn!

Both bugs are fixed in the latest version, mysqlcheck 2.4.2.
Thanks for the report!

Regards,

- Jani

For technical support contracts, visit https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Jani Tolonen
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12776@lists.mysql.com
To unsubscribe, e-mail