After power problems in the datacenter(master server powered off all
of a sudden) my master and replicating slave became not synced. I
decided to re-create the slave using innobackupex as follows:
# innobackupex-1.5.1 --stream=tar /tmp/ --slave-info | ssh slave "tar
xfi - -C ~/mysql"
After about a minute this command crashes with the following output:
>> log scanned up to (1008663005500)
>> log scanned up to (1008663286889)
>> log scanned up to (1008663565421)
>> log scanned up to (1008663831324)
innobackupex-1.5.1: Backing up files '/var/lib/mysql/db/*.ibd' (40 files)
>> log scanned up to (1008664127219)
>> log scanned up to (1008664430098)
>> log scanned up to (1008664707455)
>> log scanned up to (1008664991956)
>> log scanned up to (1008665255594)
>> log scanned up to (1008665527730)
>> log scanned up to (1008665769134)
The file 'db/foo.ibd' may not be InnoDB datafile or may be corrupted.
tar_append_tree("db/foo.ibd", "db/foo.ibd"): Input/output error
innobackupex-1.5.1: tar returned with exit code 255.
innobackupex-1.5.1: Error: Failed to stream
'/var/lib/mysql/db/foo.ibd': at /usr/bin/innobackupex-1.5.1 line 336.
This command worked just fine in the very first time when I setup the
slave but now it looks like there is a data corruption problem in the
master, right? However, there are no error entries in the master log
What would you recommend in this situation?
Best regards, Pavel