Not the answer you need?
Register and ask your own question!

What are the root causes of import failure due to errp: errors

danzhidanzhi EntrantCurrent User Role Beginner
We are using MySQL 5.5 and innobackupex-1.5.1. All but a few table backups fail to be restored and mysql.log indicates lots of [errp:page#] errors and InnoDB finally claim the .ibd file seems to be corrupted. We have run innochecksum on the file and it is fine.

We are wondering whether the .ibd file is really corrupted or the corresponding .exp file maybe be corrupted and hence is incompatible with the .ibd file? How can we identify the root cause so to have a remedy for this?


InnoDB: Using DIRECT_IO for IMPORT TABLESPACE.
InnoDB: Import: The extended import of bb_replica_1/bb_data is being started.
InnoDB: Import: 1 indexes have been detected.
InnoDB: Starting chunked import: Tue May 23 21:05:33 2017
InnoDB: chunk size: 8
InnoDB: free_limit_bytes: 11918114816
InnoDB: Progress in %: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 [errp:664701] [errp:664706] [errp:664725] [errp:664728] [errp:66473
4] [errp:664735] [errp:664759] [errp:664761] [errp:664762] [errp:664763] [errp:664764] [errp:664777] [errp:664780] [er
rp:664782] [errp:664783] [errp:664784] [errp:664785] [errp:664786] [errp:664787] [errp:664794] [errp:664795] [errp:664
796] [errp:664797] [errp:664799] [errp:664800] [errp:664801] [errp:664802] ...... [errp:727422] [errp:727423] 100 done.
InnoDB: Chunked import done: Tue May 23 21:08:30 2017
170523 21:08:30 InnoDB: Error: file './bb_replica_1/bb_data.ibd' seems to be corrupt.
InnoDB: An attempt to convert and salvage all corrupt pages was not made.
InnoDB: ##### CAUTION #####
InnoDB: ## The .ibd file may cause InnoDB to crash, even though its re-import seems to have succeeded.
InnoDB: ## If you don't know how to salvage data from a .ibd, you should not use the file.
InnoDB: ###################
170523 21:08:30 InnoDB: cannot find or open in the database directory the .ibd file of
InnoDB: table `bb_replica_1`.`bb_data`
InnoDB: in ALTER TABLE ... IMPORT TABLESPACE


file bb_data.ibd = 12041846784 bytes (734976 pages)...
checking pages in range 0 to 734975
page 18367 okay: 2.499% done
page 48255 okay: 6.566% done
page 76671 okay: 10.432% done
page 107455 okay: 14.620% done
page 139071 okay: 18.922% done
page 148223 okay: 20.167% done
page 155519 okay: 21.160% done
page 163263 okay: 22.214% done
page 172799 okay: 23.511% done
page 183039 okay: 24.904% done
page 193151 okay: 26.280% done
page 203647 okay: 27.708% done
page 213439 okay: 29.040% done
page 222527 okay: 30.277% done
page 232127 okay: 31.583% done
page 242623 okay: 33.011% done
page 252991 okay: 34.422% done
page 262975 okay: 35.780% done
page 273087 okay: 37.156% done
page 281279 okay: 38.271% done
page 288447 okay: 39.246% done
page 296063 okay: 40.282% done
page 304511 okay: 41.432% done
page 314367 okay: 42.773% done
page 323327 okay: 43.992% done
page 331007 okay: 45.037% done
page 337919 okay: 45.977% done
page 347455 okay: 47.274% done
page 356095 okay: 48.450% done
page 363647 okay: 49.478% done
page 371135 okay: 50.496% done
page 379647 okay: 51.654% done
page 387711 okay: 52.752% done
page 395519 okay: 53.814% done
page 403391 okay: 54.885% done
page 411007 okay: 55.921% done
page 419455 okay: 57.071% done
page 430975 okay: 58.638% done
page 442431 okay: 60.197% done
page 453759 okay: 61.738% done
page 464959 okay: 63.262% done
page 476351 okay: 64.812% done
page 487807 okay: 66.371% done
page 499199 okay: 67.921% done
page 510463 okay: 69.453% done
page 521727 okay: 70.986% done
page 533311 okay: 72.562% done
page 544767 okay: 74.121% done
page 556159 okay: 75.671% done
page 569983 okay: 77.551% done
page 587455 okay: 79.929% done
page 604671 okay: 82.271% done
page 622207 okay: 84.657% done
page 639935 okay: 87.069% done
page 656831 okay: 89.368% done
page 674111 okay: 91.719% done
page 691455 okay: 94.079% done
page 708735 okay: 96.430% done
page 725823 okay: 98.755% done

> hexdump -C bb_data.exp
00000000 78 70 6f 72 74 69 6e 66 00 00 00 01 62 62 5f 72 |xportinf....bb_r|
00000010 65 70 6c 69 63 61 5f 39 31 2f 62 62 5f 64 61 74 |eplica_91/bb_dat|
00000020 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |a...............|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000200 00 00 00 00 00 00 00 2f 00 00 00 03 50 52 49 4d |......./....PRIM|
00000210 41 52 59 00 00 00 00 00 00 00 00 00 00 00 00 00 |ARY.............|
00000220 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00004000

Comments

  • mirfanmirfan Database Administrator Inactive User Role Beginner
    Can you please show us exact commands for innobackupex along with my.cnf on source and destination. It seems like table is corrupted on source. Did you tried to dump bb_replica_1 table or any other table errored out (on destination during backup restore) on source via mysqldump ? Is that works fine ?
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.