Note: I have tested this dump/bug only on WIndows 32 Bit (XP/2003).
How to reproduce:
1. Download and extract latest ZIP file of Win32 MariaDB Binary Distribution (In this case, version 5.3.0 to c:\mariadb).
2. Rename my-medium.ini to my.ini (in my case, I had to add the line "skip-innodb" to avoid another InnoDB-related crash).
2. Start server in commandline window with
c:\mariadb\bin\mysqld --standalone
3. Open another commandline window and load dump:
c:\mariadb\bin\mysql -u root < c:\dump.sql
MySQL crashes with "ERROR 1034 (HY000) at line 135888: Wrong bytesec: 0- 0- 0 at 293128; Skipped"
Logfiles says: "110814 19:07:49 [Warning] Warning: Enabling keys got errno 0 on db.el, retrying"
The original table where created with MySQL and converted on MariaDB 5.2.5 from MyISAM to Aria format without error. When restoring the SQL backup from file to an Intel i7 machine, I had this error 1034 since MariaDB 5.2.5. When upgrading to version 5.3.0 on the server, I created all databases freshly from SQL dump. The bug emerged then on all machines tested:
Windows 2003 Enterprise 32 Bit, Intel Xeon Quadcore, 12GB RAM,
Windows XP 32 Bit, Intel Dual Core, 2GB RAM
Notebook Intel Single Core, 512MB RAM
Notebook Intel Dual Core, 2GB RAM
When creating the same table as MyISAM, the bug does not occur.
Dump, my.ini file and database dir after restoring is included in ariadbformatwrongbytesec.7z
The issue was a bug in Aria when using
alter table ... disable keys;
lock tables ... write;
INSERT multi-value-insert;
INSERT multi-value-insert;
If you remove the alter table command from the dump, the data loads fine.
I will push a fix to 5.2 shortly