innochecksum -s 600 ../data/test/tab1.ibd 

• --end-page= num , -e num 

End at this page number. Example usage: 

innochecksum --end-page=700 ../data/test/tab1.ibd 

or: 

innochecksum --p 700 ../data/test/tab1.ibd 

• --page= num , -p num 

Check only this page number. Example usage: 

innochecksum --page=701 ../data/test/tab1.ibd 

• --strict-check , -C 

Specify a strict checksum algorithm. Options include innodb , crc32 , and none . 

In this example, the innodb  checksum algorithm is specified: 

innochecksum --strict-check=innodb ../data/test/tab1.ibd 

In this example, the crc32  checksum algorithm is specified: 

innochecksum -C crc32 ../data/test/tab1.ibd 

The following conditions apply: 

•If you do not specify the --strict-check  option, innochecksum  validates against innodb , crc32 and none . 

•If you specify the none  option, only checksums generated by none  are allowed. 

•If you specify the innodb  option, only checksums generated by innodb  are allowed. 

•If you specify the crc32  option, only checksums generated by crc32  are allowed. 

• --no-check , -n 

Ignore the checksum verification when rewriting a checksum. This option may only be used with the innochecksum --write  option. If the --write  option is not specified, innochecksum  terminates. 

In this example, an innodb  checksum is rewritten to replace an invalid checksum: 

innochecksum --no-check --write innodb ../data/test/tab1.ibd 

• --allow-mismatches , -a 

The maximum number of checksum mismatches allowed before innochecksum  terminates. The default setting is 0. If --allow-mismatches= N , where N >=0 , N  mismatches are permitted and innochecksum  terminates at N +1 . When --allow-mismatches  is set to 0, innochecksum terminates on the first checksum mismatch. 

In this example, an existing innodb  checksum is rewritten to set --allow-mismatches  to 1. 

innochecksum --allow-mismatches=1 --write innodb ../data/test/tab1.ibd 

