# innodb\_fast\_checksum caveat

**URL:** <https://forums.percona.com/t/innodb-fast-checksum-caveat/2125>\
**Category:** Percona XtraBackup\
**Created:** [March 3, 2011, 10:57am UTC](https://forums.percona.com/t/innodb-fast-checksum-caveat/2125 "2011-03-03T10:57:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CaptTofu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/capttofu/32/9842_2.png) [@CaptTofu](https://forums.percona.com/u/CaptTofu)\
**Post date:** [March 3, 2011, 10:57am UTC](https://forums.percona.com/t/innodb-fast-checksum-caveat/2125/1 "2011-03-03T10:57:38Z")

</div>

I posted a forum issue about a page fault I had will restoring a backup made on a Ubuntu 10.04 server to a Ubuntu 9.10 server and first assumed there was some issue with the version of the OS. I had this same problem with a backup made on a Debian Lenny server and restoring on an Ubuntu 10.04 server.

It turns out that the issue is that if the backup is made on a server with “innodb\_fast\_checksum=1” turned on, you will get this error if you try to use a restored (prepared) backup on a box NOT using innodb\_fast\_checksum. This also includes using the generated backup file “backup-my.cnf”, which even if you make a backup on a server using fast checksum, this file will NOT have innodb\_fast\_checksum specified and starting MySQL with this file will result in the failure I had listed in my previous forum post:

10301 1:18:35 InnoDB: Page dump in ascii and hex (16384 bytes):  
len 16384; hex 6c641a4e00000005000000000000000000000016946dfe1600  
…  
…  
huge dump of 000s and fffs  
then:  
InnoDB: End of page dump  
110301 1:18:35 InnoDB: Page checksum 1300381512 (32bit\_calc: 1818499662), prior-to-4.0.14-form checksum 1119544184  
InnoDB: stored checksum 1818499662, prior-to-4.0.14-form stored checksum 1119544184

I don’t know if this is documented, but if it isn’t, I’d be glad to get it documented for you if you give me the details of submitting such a contribution.

---

<div class="post-metadata">

**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\
**Post date:** [March 11, 2011, 9:35pm UTC](https://forums.percona.com/t/innodb-fast-checksum-caveat/2125/2 "2011-03-11T21:35:44Z")

</div>

I will draw Fred’s attention to this. I also filed a bug against xtrabackup.

---

<div class="post-metadata">

**Author:** ![CaptTofu](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/capttofu/32/9842_2.png) [@CaptTofu](https://forums.percona.com/u/CaptTofu)\
**Post date:** [July 8, 2011, 9:21am UTC](https://forums.percona.com/t/innodb-fast-checksum-caveat/2125/3 "2011-07-08T09:21:23Z")

</div>

Hey there,

Is there a bug for this logged? It bit me again this morning, but for some reason the only way I could get around it this time was to supply “–innodb-fast-checksum” on the command line during a prepare. Maybe I’ll chat with Stew 🙂
