"marked as crashed", "zerofilling" and "wrong data in bitmap" when recovering Aria tables
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
High
|
Michael Widenius |
Bug Description
After running the engine_stress RQG scenario and recovery, mysqld reported the following:
# 2010-09-10T13:26:31 100910 13:26:31 [ERROR] mysqld: Table './test/
# 2010-09-10T13:26:31 100910 13:26:31 [Note] Zerofilling table: './test/
# 2010-09-10T13:26:31 100910 13:26:31 [Note] Zerofilling table: './test/
then CHECK TABLE `test`.
'Page 1: Wrong data in bitmap. Page_type: 1 full: 1 empty_space: 6418 Bitmap-bits: 3'
This happened on a mysqld-based recovery using existing tables. Recovery using maria_read_log and empty datadir worked as expected.
bzr version-info:
date: 2010-09-10 02:42:12 +0300
build-date: 2010-09-10 16:52:51 +0300
revno: 2928
branch-nick: 5.1
RQG command line:
/home/buildbot/
--queries=1M \
--engine=Maria \
--mysqld=
--mysqld=
--mysqld=
--mysqld=
--reporters=
--duration=120 \
--threads=5 \
--rows=100 \
--mask-level=0 \
--mysqld=
--mysqld=
--mysqld=
--mysqld=
--mysqld=
--mask=59718 \
--queries=100000000 \
--mask=59718 \
--seed=time \
--basedir=. \
--vardir=
--grammar=
--gendata=
Changed in maria: | |
status: | New → In Progress |
Changed in maria: | |
milestone: | none → 5.1 |
Changed in maria: | |
status: | Fix Committed → Fix Released |
Found bug, fixed, tested and pushed in 5.1
- Tables marked as opened was not properly unmarked on recovery if there was not changes since checkpoint
- zerofill of tables put wrong data in bitmap if directory for page was full
- Tables was thought as 'moved' during recovery if they had a create_lsn bigger than the lsn in the control file.