maria-discuss team mailing list archive

[Ian Gilfillan <ian@xxxxxxxxxxx>]

I found Spider tables extremely easy to corrupt when I was looking at 
Spider (see e.g. https://mariadb.atlassian.net/browse/MDEV-5559), so 
eventually stopped exploring.

Unhelpfully, this was in January and I can't remember what I used to do 
to recover, except that I used it often! Perhaps manual deletion?

ian


On 27/05/2014 12:29, Federico Razzoli wrote:
> It seems I've played too much with bug 6269:
>
> https://mariadb.atlassian.net/browse/MDEV-6269
>
> As a result, a table has crashed:
>
> MariaDB [test]> DROP TABLE user;
> ERROR 1051 (42S02): Unknown table 'test.user'
> MariaDB [test]> REPAIR TABLE user;
> +-----------+--------+----------+---------------------------------+
> | Table     | Op     | Msg_type | Msg_text                        |
> +-----------+--------+----------+---------------------------------+
> | test.user | repair | Error    | Table 'test.user' doesn't exist |
> | test.user | repair | status   | Operation failed                |
> +-----------+--------+----------+---------------------------------+
> 2 rows in set (0.00 sec)
>
> Errlog agrees:
>
> 140527 12:23:56 [ERROR] mysqld: Table './mysql/spider_tables' is marked as crashed and should be repaired
>
> The question is: how should I repair it? mysql.spider_tables is already empty. REPAIR TABLE does not work. Can't find a variable to force recovery on restart. DROP and CREATE OR REPLACE are impossible, as shown above.
>
> Is there another way?
> Should I report this as a bug?
>
> Regards
> Federico
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp