MySQL Bugs: #35048: maria table corruption reported when transactional=0

Bug #35048	maria table corruption reported when transactional=0
Submitted:	4 Mar 2008 19:03	Modified:	8 Mar 2008 0:13
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Maria storage engine	Severity:	S2 (Serious)
Version:	5.1.24 (mysql-maria tree)	OS:	Any
Assigned to:	Michael Widenius	CPU Architecture:	Any

Description:
importing the the attached .sql file causes check table to report corruption when the table is created as non-transactional.

mysql> check table t1;
+---------+-------+----------+---------------------------------------------------------------------------------+
| Table   | Op    | Msg_type | Msg_text                                                                        |
+---------+-------+----------+---------------------------------------------------------------------------------+
| test.t1 | check | warning  | Table is marked as crashed                                                      |
| test.t1 | check | error    | Page 4:  Wrong data in bitmap.  Page_type: 1  empty_space: 6958  Bitmap-bits: 1 |
| test.t1 | check | error    | Corrupt                                                                         |
+---------+-------+----------+---------------------------------------------------------------------------------+
3 rows in set (0.00 sec)

How to repeat:
run attached sql in mysql client

testcase

Attachment: bug35048.sql (application/unknown, text), 39.75 KiB.

The UPDATE towards the end is not needed on my machine. The very first DELETE isn't either.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html