Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"

core binary datadir
LPexportBug619731_var-bug619731.zip

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
This is probably fixed by my last pushed fix for bitmap pages. I will run the test case 5 times to try to ensure this case is also fixed.

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
I am afraid this corruption still happened with the following revision:

revision-id: monty@askmonty.org-20100915130103-x6i3x2mjc5gxsu77
date: 2010-09-15 16:01:03 +0300
build-date: 2010-09-20 12:05:51 +0300
revno: 2938
branch-nick: 5.1

I will upload the datadir shortly.

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
RQG command line:

/home/buildbot/randgen/runall.pl \
--queries=1M \
--engine=Maria \
-mysqld=-default-storage-engine=Maria \
-mysqld=-safe-mode \
-mysqld=-sync-sys=0 \
-mysqld=-log-output=file \
-mysqld=-maria_log_purge_type=at_flush \
--reporters=ErrorLog,Backtrace,Recovery,Shutdown \
--duration=30 \
--threads=1 \
--rows=1000 \
--mask-level=1 \
-mysqld=-maria-repair-threads=2 \
-mysqld=-loose-maria-group-commit=soft \
-mysqld=-loose-maria_group_commit_interval=100 \
-mysqld=-maria-checkpoint-interval=1 \
-mysqld=-maria-block-size=4K \
--mask=41440 \
--queries=100000000 \
--mask=41440 \
--seed=time \
--basedir=. \
-mysqld=-init-file=/home/buildbot/randgen/conf/smf/smf2.sql \
--grammar=conf/smf/smf2.yy

RQG command line:

/home/buildbot/randgen/runall.pl \
--queries=1M \
--engine=Maria \
-mysqld=-default-storage-engine=Maria \
-mysqld=-safe-mode \
-mysqld=-sync-sys=0 \
-mysqld=-log-output=file \
-mysqld=-maria_log_purge_type=at_flush \
--reporters=ErrorLog,Backtrace,Recovery,Shutdown \
--duration=30 \
--threads=1 \
--rows=1000 \
--mask-level=1 \
-mysqld=-maria-repair-threads=2 \
-mysqld=-loose-maria-group-commit=soft \
-mysqld=-loose-maria_group_commit_interval=100 \
-mysqld=-maria-checkpoint-interval=1 \
-mysqld=-maria-block-size=4K \
--mask=41440 \
--queries=100000000 \
--mask=41440 \
--seed=time \
--basedir=. \
-mysqld=-init-file=/home/buildbot/randgen/conf/smf/smf2.sql \
--grammar=conf/smf/smf2.yy

datadir, logs, etc.
LPexportBug619731_var-bug619731-2.zip

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
Still present with the following revision:

revno: 2951
committer: Michael Widenius <monty@askmonty.org>
branch nick: maria-5.1
timestamp: Wed 2010-10-13 18:15:43 +0300
message:
Fixes for bugs found by running test case for LP#608369 "Page: 1 Found wrong page type 0' on CHECK TABLE EXTENDED"
Fixed overflow when using long --debug=xxxxxx line.
Fixed that "mysqld --disable-debug --debug" works.
Ensure that MariaDB doesn't start if the Aria engine didn't start and we are using Aria for temporary tables.
More DBUG_ASSERT() and more info in debug log.

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
After a LOT of work and thinking, I finally nailed down a corruption in the bitmaps.
The bug happens when deleting a row spanning many pages and there is new data inserted on the same page during one checkpoint and the new data pages are flushed out.
I will push a fix for this in 5.1 tomorrow morning (after I have run testing on the patch the whole night).

Re: Aria recovery corruption "Page 1: Row: 1 has an extent with wrong information in bitmap"
Fixed and committed yesterday a related bug. Now I can't repeat any problems anymore with the given test cases.
Fix is also pushed to 5.2 tree.

Launchpad bug id: 619731