Znikające tabele po konwersacji do innodb

[dong 0]

Krew mnie zalewa. Brakowało mi plików MYI w

innodb_index_stats.frm 12982Dec 13 20:40

innodb_index_stats.ibd 98304Dec 13 20:40

innodb_table_stats.frm 8830Dec 13 20:40

innodb_table_stats.ibd 98304Dec 13 20:40

usunalem w/w pliki, ale dalej pojawia sie problem.

Po reboocie serwera W logach mam tylko tyle:

2014-01-03 19:05:15 18343 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-03 19:05:15 18343 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-01-03 19:05:15 18343 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-03 19:05:15 18343 [Note] InnoDB: Using CPU crc32 instructions
2014-01-03 19:05:15 18343 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-03 19:05:15 18343 [Note] InnoDB: Completed initialization of buffer pool
2014-01-03 19:05:15 18343 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-03 19:05:15 18343 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure you are using the right ib_logfi
les to start up the database. Log sequence number in the ib_logfiles is 1600617, logsequence numbers stamped to ibdata file headers are between 10050273432 and 10050273432.
2014-01-03 19:05:15 18343 [Note] InnoDB: The log sequence numbers 10050273432 and 10050273432 in ibdata files do not match the log sequence number 1600617 in the ib_logfiles!
2014-01-03 19:05:15 18343 [Note] InnoDB: Database was not shutdown normally!
2014-01-03 19:05:15 18343 [Note] InnoDB: Starting crash recovery.
2014-01-03 19:05:15 18343 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-03 19:05:15 18343 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace alfa_kopia/vb_blog_pinghistory uses space ID: 82 at filepath: ./alfa_kopia/vb_bl
og_pinghistory.ibd. Cannot open tablespace alfa_kopia/vb_postrelease which uses space ID: 82 at filepath: ./alfa_kopia/vb_postrelease.ibd
2014-01-03 19:05:15 802807400  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./alfa_kopia/vb_postrelease.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
140103 19:05:15 mysqld_safe mysqld from pid file /var/db/mysql/ns352115.ip-91-121-79.eu.pid ended

Włączałem innodb force recovery = 4. serwer startuje, w phpmyadmin wyskakuje ze dana tabela doesnt exist. chmody i chown sa ok.

W my.cnf mam tylko tyle, moze tu jest przyczyna:

datadir = /home/mysql

Pliki mysql znajduja sie w home/mysql, a w var/db (taki standard freebsd) znajduje sie symblink. Moj system to FreeBSD.

Proszę o pomoc.

 

[Miłosz 2311]

Brakowało mi plików MYI w

innodb_index_stats.frm 12982Dec 13 20:40

innodb_index_stats.ibd 98304Dec 13 20:40

innodb_table_stats.frm 8830Dec 13 20:40

innodb_table_stats.ibd 98304Dec 13 20:40

usunalem w/w pliki, ale dalej pojawia sie problem.

 

Przy innodb nie ma plików MYI w tabelach. Informacje o tabelach są przechowywane także w ibdata. Jeśli masz backup (a napewno masz ), to najprostrzym sposobem jest wywalenie plików z katalogu bazy, wywalenie ibdata i logfiles, przeładowanie mysqla i wgranie backupu. Zakładam, że jest to jedna baza, a nie XX baz

[dong 0]

No ok, wgram jakiś stary backup, ale czy to normalne, że przy zwykłym reboocie baza poleciała w kosmos? Wczesniej mialem myisam i nie bylo takich problemow.

[Miłosz 2311]

No ale wcześniej napisałeś, że wywaliłeś pliki tabel innodb, więc dlaczego zrzucasz wine na reboota? Ty je wywaliłeś czy reboot?