maria-discuss team mailing list archive

[kentoku <kentokushiba@xxxxxxxxx>]

Hi Federico,

> Yes, I repaired mysql.spider_tables. But the problem with the `user` table remains. Since I could not find any solution, I reported this bug:
> https://mariadb.atlassian.net/browse/MDEV-6293

ok, I'll check it.

Thanks,
Kentoku


2014-06-04 5:04 GMT+09:00 Federico Razzoli <federico_raz@xxxxxxxx>:
> Hi Kentoku
>
> Yes, I repaired mysql.spider_tables. But the problem with the `user` table remains. Since I could not find any solution, I reported this bug:
> https://mariadb.atlassian.net/browse/MDEV-6293
>
> Regards
> Federico
>
>
> --------------------------------------------
> El mar, 3/6/14, kentoku <kentokushiba@xxxxxxxxx> escribió:
>
>  Asunto: Re: [Maria-discuss] Repairing a SPIDER table
>  Para: "Federico Razzoli" <federico_raz@xxxxxxxx>
>  CC: "Maria Discuss" <maria-discuss@xxxxxxxxxxxxxxxxxxx>
>  Fecha: martes, 3 de junio, 2014 21:46
>
>  Hi Federico and Ian,
>
>  > 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).
>
>  This is bug of Spider's
>  table discovery feature. I'll fix this bug
>  soon. Please use "create table"
>  statement with column definitions for
>  now.
>
>  >
>  [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.
>
>  Did you try "repair table
>  mysql.spider_tables"?
>
>  Thanks,
>  Kentoku
>
>
>  2014-05-27
>  21:09 GMT+09:00 Federico Razzoli <federico_raz@xxxxxxxx>:
>  > 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 <ian@xxxxxxxxxxx>
>  escribió:
>  >
>  >
>  Asunto: Re: [Maria-discuss] Repairing a SPIDER table
>  >  Para: maria-discuss@xxxxxxxxxxxxxxxxxxx
>  >  Fecha: martes, 27 de mayo, 2014 12:51
>  >
>  >  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
>  >  >
>  >  >
>  >
>  >
>  >
>  _______________________________________________
>  >  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
>  >
>  >
>  >
>  _______________________________________________
>  > 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
>
> _______________________________________________
> 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