Sorry for flooding. I've read your bug report, Ian. If I understand correctly, SPIDER ignores the CONNECTION option. So 6268 and 5559 could be the same bug (both with incorrect title: in 6268, Elena's comment explains the problem).
Federico
--------------------------------------------
El mar, 27/5/14, Ian Gilfillan
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@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp