INFORMATION_SCHEMA.INNODB_CHANGED_PAGES query fails server with an I/O error if a bitmap file in the middle of requested range is missing

[Laurynas Biveinis]

If a INNODB_CHANGED_PAGES query needs a bitmap file range with one of the files missing in the middle of the range, then the server will stop with an I/O error on a debug build, probably on a release build as well.

To reproduce, add the following to the end of innodb_changed_pages.test, before the final DROP TABLE t1:

let $MYSQLD_DATADIR= `select @@datadir`;
# --replace_regex /_[[:digit:]]+\.xdb$//
list_files $MYSQLD_DATADIR ib_modified_log*;

remove_files_wildcard $MYSQLD_DATADIR ib_modified_log_4_*.xdb;

# --replace_regex /_[[:digit:]]+\.xdb$//
list_files $MYSQLD_DATADIR ib_modified_log*;

SELECT COUNT(*) FROM INFORMATION_SCHEMA.INNODB_CHANGED_PAGES
       WHERE START_LSN > 10000;

Discovered while working on XtraBackup, as the bitmap file reader is shared between XtraDB and XtraBackup. The fix will be to take the XtraBackup reader robustness improvements.

Triaging as Medium instead of High, because impossible to reproduce without write access to the server data dir.

[Laurynas Biveinis (laurynas-biveinis)]

See bug 1184468

[Laurynas Biveinis (laurynas-biveinis)]

See bug 1184427.

[Laurynas Biveinis (laurynas-biveinis)]

See bug 1191580.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-360