OVH Community, votre nouvel espace communautaire.

Récupération BDD mySQL après crash disque


janus57
13/09/2016, 18h52
Bonjour,

visiblement d'après les info que l'on peu trouver il faut les fichier en .frm sinon c'est foutu.
You must have:

-ibdata1

-ib_logfile0

-ib_logfile1

-.FRM files from your mysql_database folder
Cf : http://dba.stackexchange.com/questio...and-a-ibd-file

Après peut être que c'est plus vrai, mais de mémoire InnoDB est plus capricieux que MyISAM pour faire du "recovery".

Cordialement, janus57

buddy
12/09/2016, 23h38
les conseils de la page http://dev.mysql.com/doc/refman/5.5/...-recovery.html ne marche pas ?

Shogoki
12/09/2016, 23h22
J'ai réussi à passer à plusieurs étapes non sans mal mais maintenant je suis bloqué avec cette erreur (mysqld ne se lance pas)

le log

Code:
160912 19:04:55 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160912 19:04:55 [Note] libgovernor.so not found
160912 19:04:55 [Note] /usr/libexec/mysqld (mysqld 5.5.51-cll-lve) starting as process 14774 ...
160912 19:04:55 [Note] Plugin 'FEDERATED' is disabled.
160912 19:04:55 InnoDB: The InnoDB memory heap is disabled
160912 19:04:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160912 19:04:55 InnoDB: Compressed tables use zlib 1.2.3
160912 19:04:55 InnoDB: Using Linux native AIO
160912 19:04:55 InnoDB: Initializing buffer pool, size = 128.0M
160912 19:04:55 InnoDB: Completed initialization of buffer pool
160912 19:04:55 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160912 19:04:55  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160912 19:04:55  InnoDB: Error: page 131073 log sequence number 917213087932
InnoDB: is in the future! Current system log sequence number 769927657085.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160912 19:04:55  InnoDB: Error: page 49153 log sequence number 917213015204
InnoDB: is in the future! Current system log sequence number 769927657085.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160912 19:04:55  InnoDB: Error: page 196609 log sequence number 917213088228
InnoDB: is in the future! Current system log sequence number 769927657085.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160912 19:04:55  InnoDB: Error: page 202763 log sequence number 917213199667
InnoDB: is in the future! Current system log sequence number 769927657085.
...
...
...
160912 19:04:55  InnoDB: Assertion failure in thread 139951258429408 in file fil0fil.c line 4578
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:04:55 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338555 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x795ffe]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x67db23]
/lib64/libpthread.so.0(+0xf7e0)[0x7f48f0c9d7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f48ef0e25e5]
/lib64/libc.so.6(abort+0x175)[0x7f48ef0e3dc5]
/usr/libexec/mysqld[0x89539b]
/usr/libexec/mysqld[0x8712c2]
/usr/libexec/mysqld[0x871baa]
/usr/libexec/mysqld[0x866c55]
/usr/libexec/mysqld[0x836b03]
/usr/libexec/mysqld[0x836d88]
/usr/libexec/mysqld[0x839b53]
/usr/libexec/mysqld[0x825b6c]
/usr/libexec/mysqld[0x7f15b0]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x6807c1]
/usr/libexec/mysqld[0x592638]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x928)[0x596228]
/usr/libexec/mysqld[0x51b228]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x3fd)[0x51de9d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f48ef0ced1d]
/usr/libexec/mysqld[0x513225]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
160912 19:04:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Shogoki
11/09/2016, 22h52
Bonjour à tous

Mon disque sur le serveur a craché...

Conclusion plusieurs fichiers ont disparus...


Pour ma BDD, j'ai réussi à récupérer les fichiers suivant
ibdata1
ib_logfile0
ib_logfile1

Malheureusement plusieurs fichiers .frm manquent... c'est pourquoi, je ne trouve pas de tutorial pour récupérer facilement les données dans les fichiers ci-dessus.

Pouvez-vous me dire si c'est possible de reconstruire la BDD avec ces 3 fichiers ?
Et si oui, comment???

Je suis pas du tout un pro en linux mais j'apprends vite

Merci


Serveur dédié centos 6/ plesk 11.5