Bug #34734 5.1.15 ndb-6.1.23 upgraded to 5.1.23 ndb-6.2.12 cannot repare ndb_binlog_index

• Submitted: 21 Feb 2008 16:20
• Modified: 1 Apr 2009 2:20
• Reporter: Bogdan Kecman
• Status: No Feedback
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: telco 5.1.23 ndb-6.2.12
• OS: Any
• Assigned to: Assigned Account
• CPU Architecture: Any
• Tags: mccge, ndb_binlog_index, upgrade

[21 Feb 2008 16:20] Bogdan Kecman

Description:
This fails:

setup 5.1.15 ndb-6.1.23 to include ndb_binlog_index table

upgrade 5.1.15 ndb-6.1.23 to 5.1.23 ndb-6.2.12 

corrupt ndb_binlog_index 
 # echo "jsdflsdjfhlsdhfs1111111" > ndb_binlog_index.MYD

try repair

This Works
setup 5.1.23 ndb-6.2.12
corrupt ndb_binlog_index
try repair

How to repeat:

setup 5.1.15 ndb-6.1.23 to include ndb_binlog_index table

upgrade 5.1.15 ndb-6.1.23 to 5.1.23 ndb-6.2.12 

corrupt ndb_binlog_index 
 # echo "jsdflsdjfhlsdhfs1111111" > ndb_binlog_index.MYD

try repair

mysql> REPAIR TABLE ndb_binlog_index;
+------------------------+--------+----------+------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+------------------------------------------+
| mysql.ndb_binlog_index | repair | info | Wrong bytesec: 110-110-110 at 0; Skipped |
| mysql.ndb_binlog_index | repair | status | OK |
+------------------------+--------+----------+------------------------------------------+
2 rows in set (0.00 sec)

mysql> check table ndb_binlog_index;
+------------------------+-------+----------+---------------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+-------+----------+---------------------------------------------------------------+
| mysql.ndb_binlog_index | check | Error | Incorrect information in file: './mysql/ndb_binlog_index.frm' |
| mysql.ndb_binlog_index | check | error | Corrupt |
+------------------------+-------+----------+---------------------------------------------------------------+
2 rows in set (0.00 sec)

Suggested fix:
n/a

[21 Feb 2008 16:50] Bogdan Kecman

If used like this then repair works:

0. 6.1 setup to include ndb_binlog_index table
1. 6.1 -> 6.2 upgrade
1a. dump of ndb_binlog_index
1b. drop / create of ndb_binlog_index
1c. insert old data from dump
2. corrupt ndb_binlog_index
3. try repair - now it works

[21 Feb 2008 16:53] Bogdan Kecman

I tried the same procedure with all mysql/*.MYD ...
MySQL is not able to repair them after the upgrade

[1 Mar 2009 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

[1 Apr 2009 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".