Bug #38113 corruption, and got error 175 when reading table, and cannot find record ...

• Submitted: 14 Jul 2008 20:23
• Modified: 22 Aug 2008 14:04
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Can't repeat
• Category: MySQL Server: Maria storage engine
• Severity: S3 (Non-critical)
• Version: 5.1.25-maria-alpha-debug
• OS: Windows
• Assigned to: Sergei Golubchik
• CPU Architecture: Any

[14 Jul 2008 20:23] Shane Bester

Description:
After some inserts I found these errors in the logs:

Version: '5.1.25-maria-alpha-debug'  socket: ''  port: 3306  Source distribution
080714 22:20:16 [ERROR] Got error 175 when reading table '.\test\table66'
080714 22:20:16 [ERROR] Got error 175 when reading table '.\test\table66'
080714 22:20:57 [ERROR] Got error 176 when reading table '.\test\table66'
080714 22:20:59 [ERROR] Got error 176 when reading table '.\test\table66'
080714 22:21:46 [ERROR] Got error 176 when reading table '.\test\table66'
080714 22:21:46 [ERROR] Got error 176 when reading table '.\test\table66'
080714 22:22:00 [ERROR] Got error 175 when reading table '.\test\table56'
080714 22:22:00 [ERROR] Got error 175 when reading table '.\test\table56'

the codes mean:
#define HA_ERR_FILE_TOO_SHORT	  175	 /* File too short */
#define HA_ERR_WRONG_CRC	  176	 /* Wrong CRC on page */

How to repeat:
wait and see.

[15 Jul 2008 8:42] MySQL Verification Team

sometimes there is nothing in the error log, but queries are failing like this:

(1032)- Can't find record in 'table66': update ignore `table66` set `co [...]
(1030)- Got error 175 from storage engine: delete from `table66` where `co [...]

[15 Jul 2008 10:17] MySQL Verification Team

this is a corruption really:  after that 

Table is marked as crashed
Page 2:  Wrong data in bitmap.  Page_type: 1  empty_space: 4677  Bitmap-bits: 4
Corrupt

[15 Jul 2008 13:29] MySQL Verification Team

testcase. import into mysql client.

Attachment: bug38113_testcase.sql (application/unknown, text), 9.21 KiB.

[15 Jul 2008 15:42] MySQL Verification Team

+--------------+-------+----------+---------------------------------------------------------------------------------+
| Table        | Op    | Msg_type | Msg_text                                                                        |
+--------------+-------+----------+---------------------------------------------------------------------------------+
| test.table66 | check | warning  | Table is marked as crashed                                                      |
| test.table66 | check | error    | Page 1:  Wrong data in bitmap.  Page_type: 1  empty_space: 6994  Bitmap-bits: 4 |
| test.table66 | check | error    | Corrupt                                                                         |
+--------------+-------+----------+---------------------------------------------------------------------------------+
3 rows in set (0.23 sec)

mysql 6.0-maria > show create table table66;
ERROR 1034 (HY000): Incorrect key file for table 'table66'; try to repair it
mysql 6.0-maria > show variables like "%version%";
+-------------------------+--------------------------+
| Variable_name           | Value                    |
+-------------------------+--------------------------+
| protocol_version        | 10                       |
| version                 | 6.0.6-alpha-nt-debug-log |
| version_comment         | Source distribution      |
| version_compile_machine | ia32                     |
| version_compile_os      | Win32                    |
+-------------------------+--------------------------+
5 rows in set (0.06 sec)

mysql 6.0-maria >

[15 Jul 2008 15:45] MySQL Verification Team

Thank you for the bug report.

[22 Aug 2008 14:04] Sergei Golubchik

Apparently fixed by some other recent bugfix.