MySQL Bugs: #21467: Manual URL wrong in InnoDB "page corrupted" error report

Bug #21467	Manual URL wrong in InnoDB "page corrupted" error report
Submitted:	7 Aug 2006 1:27	Modified:	20 Jun 2010 1:13
Reporter:	Arjen Lentz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	All	OS:	Any (All)
Assigned to:	Marko Mäkelä	CPU Architecture:	Any

Description:
When InnoDB reports a corrupted data page in the error log, the referring URL is incorrect.

[...]
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.

How to repeat:
See above error log excerpt.

Suggested fix:
a) fix up URL in code
b) docs/web team add URL redirect to deal with old instances.

For MySQL 5.0 the proper URL is http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html

Added mapping to correct Manual page in renamed-nodes.txt file - http://lists.mysql.com/commits/10093

Leaving in Verified status for dev to fix in server code.

Marko,

can you fix this in 5.0 and 5.1?

Regards,

Heikki

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/10392

ChangeSet@1.2274, 2006-08-15 01:42:57+02:00, tsmith@production.mysql.com +21 -0
  Applied innodb-5.1-ss677, -ss680, -ss713, and -ss720 snapshots.
  All but ss677 are against the mysql-5.1 tree only.
  
  Fixes the following bugs:
  - Bug #19834: Using cursors when running in READ-COMMITTED can cause InnoDB to crash
  - Bug #20213: DBT2 testing cause mysqld to core using Innodb
  - Bug #20493: on partition tables, select and show command casue server crash
  - Bug #21113: Duplicate printout in SHOW INNODB STATUS
  - Bug #21313: rsql_..._recover_innodb_tmp_table is redundant and broken
  - Bug #21467: Manual URL wrong in InnoDB "page corrupted" error report

fixed by inno patchset merged into 5.1.12-beta (5.1-new-maint)

Pushed to 5.0.25.

Closed (no documentation needed).

Confirmed closed.

Pushed to 5.1.12

Pushed into 5.1.47 (revid:joro@sun.com-20100505145753-ivlt4hclbrjy8eye) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Push resulted from incorporation of InnoDB tree. No changes pertinent to this bug. Re-closing.

Pushed into mysql-next-mr (revid:alik@sun.com-20100524190136-egaq7e8zgkwb9aqi) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (pib:16)

Pushed into 6.0.14-alpha (revid:alik@sun.com-20100524190941-nuudpx60if25wsvx) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Pushed into 5.5.5-m3 (revid:alik@sun.com-20100524185725-c8k5q7v60i5nix3t) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Push resulted from incorporation of InnoDB tree. No changes pertinent to this bug.
Re-closing.

Pushed into 5.1.47-ndb-7.0.16 (revid:martin.skold@mysql.com-20100617114014-bva0dy24yyd67697) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Pushed into 5.1.47-ndb-6.2.19 (revid:martin.skold@mysql.com-20100617115448-idrbic6gbki37h1c) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)

Pushed into 5.1.47-ndb-6.3.35 (revid:martin.skold@mysql.com-20100617114611-61aqbb52j752y116) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)