innochecksum
offline InnoDB file checksum utility
Synopsis
innochecksum
[options] file_name
add an example, a script, a trick and tips
examples
/usr/local/mysql-S4/bin/innochecksum /home/mysql/data-S4/auditor/*.ibd
example added by an anonymous user
description
innochecksum
prints checksums for InnoDB files. This tool reads an InnoDB
tablespace file, calculates the checksum for each page,
compares the calculated checksum to the stored checksum, and
reports mismatches, which indicate damaged pages. It was
originally developed to speed up verifying the integrity of
tablespace files after power outages but can also be used
after file copies. Because checksum mismatches will cause
InnoDB to deliberately shut down a running server, it can be
preferable to use this tool rather than waiting for a server
in production usage to encounter the damaged pages.
innochecksum
cannot be used on tablespace files that the server already
has open. For such files, you should use CHECK TABLE to
check tables within the tablespace.
If checksum
mismatches are found, you would normally restore the
tablespace from backup or start the server and attempt to
use mysqldump to make a backup of the tables within
the tablespace.
Invoke
innochecksum like this:
shell>
innochecksum [options]
file_name
innochecksum
supports the following options. For options that refer to
page numbers, the numbers are zero-based.
•
-c
Print a count
of the number of pages in the file.
•
-d
Debug mode;
prints checksums for each page.
•
-e num
End at this
page number.
•
-p num
Check only this
page number.
•
-s num
Start at this
page number.
•
-v
Verbose mode;
print a progress indicator every five seconds.
copyright
Copyright © 1997, 2013, Oracle and/or its affiliates. All rights
reserved.
This software and related documentation are provided under a
license agreement containing restrictions on use and disclosure
and are protected by intellectual property laws. Except as
expressly permitted in your license agreement or allowed by law,
you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or
display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software,
unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without
notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.
If this software or related documentation is delivered to the
U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related
documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such,
the use, duplication, disclosure, modification, and adaptation
shall be subject to the restrictions and license terms set forth
in the applicable Government contract, and, to the extent
applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer
Software License (December 2007). Oracle USA, Inc., 500 Oracle
Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of
information management applications. It is not developed or
intended for use in any inherently dangerous applications,
including applications which may create a risk of personal
injury. If you use this software in dangerous applications, then
you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure the safe use of
this software. Oracle Corporation and its affiliates disclaim any
liability for any damages caused by use of this software in
dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. MySQL is a trademark of Oracle Corporation and/or its
affiliates, and shall not be used without Oracle’s express
written authorization. Other names may be trademarks of their
respective owners.
This software and documentation may provide access to or
information on content, products, and services from third
parties. Oracle Corporation and its affiliates are not
responsible for and expressly disclaim all warranties of any kind
with respect to third-party content, products, and services.
Oracle Corporation and its affiliates will not be responsible for
any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services.
This document in any form, software or printed matter, contains
proprietary information that is the exclusive property of Oracle.
Your access to and use of this material is subject to the terms
and conditions of your Oracle Software License and Service
Agreement, which has been executed and with which you agree to
comply. This document and information contained herein may not be
disclosed, copied, reproduced, or distributed to anyone outside
Oracle without prior written consent of Oracle or as specifically
provided below. This document is not part of your license
agreement nor can it be incorporated into any contractual
agreement with Oracle or its subsidiaries or affiliates.
This documentation is NOT distributed under a GPL license. Use of
this documentation is subject to the following terms:
You may create a printed copy of this documentation solely for
your own personal use. Conversion to other formats is allowed as
long as the actual content is not altered or edited in any way.
You shall not publish or distribute this documentation in any
form or on any media, except if you distribute the documentation
in a manner similar to how Oracle disseminates it (that is,
electronically for download on a Web site with the software) or
on a CD-ROM or similar medium, provided however that the
documentation is disseminated together with the software on the
same medium. Any other use, such as any dissemination of printed
copies or use of this documentation, in whole or in part, in
another publication, requires the prior written consent from an
authorized representative of Oracle. Oracle and/or its affiliates
reserve any and all rights to this documentation not expressly
granted above.
For more information on the terms of this license, or for details
on how the MySQL documentation is built and produced, please
visit MySQL Contact &
Questions.
For additional licensing information,
including licenses for third-party libraries used by MySQL
products, see Preface and Legal Notices.
For help with using MySQL, please visit
either the MySQL
Forums or MySQL Mailing Lists where you can discuss your issues with other MySQL
users.
For additional documentation on MySQL
products, including translations of the documentation into other
languages, and downloadable versions in variety of formats,
including HTML and PDF formats, see the MySQL Documentation Library.
innochecksum
innochecksum prints checksums for InnoDB files.
This tool reads an InnoDB tablespace file, calculates the
checksum for each page, compares the calculated checksum to the
stored checksum, and reports mismatches, which indicate damaged
pages. It was originally developed to speed up verifying the
integrity of tablespace files after power outages but can also be
used after file copies. Because checksum mismatches will cause
InnoDB to deliberately shut down a running server, it can be
preferable to use this tool rather than waiting for a server in
production usage to encounter the damaged pages.
innochecksum cannot be used on tablespace files that the
server already has open. For such files, you should use CHECK
TABLE to check tables within the tablespace.
If checksum mismatches are found, you would normally restore the
tablespace from backup or start the server and attempt to use
mysqldump to make a backup of the tables within the
tablespace.
Invoke innochecksum like this:
shell> innochecksum [options]
file_name
innochecksum supports the following options. For options
that refer to page numbers, the numbers are zero-based.
• -c
Print a count of the number of pages in the file.
• -d
Debug mode; prints checksums for each page.
• -e num
End at this page number.
• -p num
Check only this page number.
• -s num
Start at this page number.
• -v
Verbose mode; print a progress indicator every five seconds.
see also
For
more information, please refer to the MySQL Reference
Manual, which may already be installed locally and which is
also available online at
http://dev.mysql.com/doc/.
author
Oracle
Corporation (http://dev.mysql.com/).