* 250GB table - PARTITIONed InnoDB; file_per_table
* RBR used
* Slave is hosed
* Sane ways of repairing the slave has been ruled out (it's a long story).
Plan A: Reload PARTITIONs by copying .ibd files. -- Rumor has it that
this will fail due to tablespace number (or something) being buried in
each .ibd. Such would make file copies of .ibd from a different machine
Question 1: Is this rumor true?
Plan B: We have a mysqldump and could reload. But, will RBR be
confused by the InnoDB blocks being slightly different after this load.
Question 2: What is the low level info in a RBR item? Does it include
a 'block number', which would probably be invalid after the reload? Or
does it contain something like the PK, which should be impervious?
Rick James - MySQL Geek