I'm getting errors on CREATE TALBE and INSERT from a mysqldump, where the error appears to be coming from Windows AIO.
I recently setup a system that will become my development workstation:
* Windows 7 Professional, version 6.1, Build 7601: Service Pack 1)
* MySQL 5.1.56
* Innodb engine
* file-per-table
I loaded a mysqldump from my old production machine (MySQL 4.1, 32-bit, Windows) and it loaded fine. I then upgraded to a new production server running MySQL 5.1.56, 64-bit, WindowsServer 2008 R2, version 6.1 , build 7601 service pack 1.
Then I did a mysqldump from my production db, and tried to load it on my test db. When I loaded the script with just the CREATE TABLE statements (~840 tables), a few tables gave errors:
ERROR 1005 (HY000) at line 41: Can't create table 'localtest.asset_type_drive_forces' (errno: 135)
Here is a section from the error log:
110822 16:09:29 InnoDB: Error: Write to file .\localtest\asset_type_drive_forces.ibd failed at offset 0 0.
InnoDB: 65536 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 5.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
110822 16:09:29 InnoDB: Warning: cannot create table `localtest`.`asset_type_drive_forces` because tablespace full
There is tons of disk space, and I just had the table containing data the previous day. I got the error on about 5 out of 840 tables. So I copied the CREATE TABLE statements from the big script to a separate script. Ran that ok, so no problem with the table schema.
Then I tried to load the records into the table, and I get:
110822 22:23:01 InnoDB: Operating system error number 5 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory. It may also be you have created a subdirectory
InnoDB: of the same name as a data file.
InnoDB: File name .\localtest\adjusted_factor_return.ibd
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
There is nothing unusual about the adjusted_factor_return table.
It seems to me that MySQL is having trouble with the file i/o calls to Windows.
I searched forums and web and could not find this problem described. Any help would be greatly appreciated.
I recently setup a system that will become my development workstation:
* Windows 7 Professional, version 6.1, Build 7601: Service Pack 1)
* MySQL 5.1.56
* Innodb engine
* file-per-table
I loaded a mysqldump from my old production machine (MySQL 4.1, 32-bit, Windows) and it loaded fine. I then upgraded to a new production server running MySQL 5.1.56, 64-bit, WindowsServer 2008 R2, version 6.1 , build 7601 service pack 1.
Then I did a mysqldump from my production db, and tried to load it on my test db. When I loaded the script with just the CREATE TABLE statements (~840 tables), a few tables gave errors:
ERROR 1005 (HY000) at line 41: Can't create table 'localtest.asset_type_drive_forces' (errno: 135)
Here is a section from the error log:
110822 16:09:29 InnoDB: Error: Write to file .\localtest\asset_type_drive_forces.ibd failed at offset 0 0.
InnoDB: 65536 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 5.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
110822 16:09:29 InnoDB: Warning: cannot create table `localtest`.`asset_type_drive_forces` because tablespace full
There is tons of disk space, and I just had the table containing data the previous day. I got the error on about 5 out of 840 tables. So I copied the CREATE TABLE statements from the big script to a separate script. Ran that ok, so no problem with the table schema.
Then I tried to load the records into the table, and I get:
110822 22:23:01 InnoDB: Operating system error number 5 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory. It may also be you have created a subdirectory
InnoDB: of the same name as a data file.
InnoDB: File name .\localtest\adjusted_factor_return.ibd
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
There is nothing unusual about the adjusted_factor_return table.
It seems to me that MySQL is having trouble with the file i/o calls to Windows.
I searched forums and web and could not find this problem described. Any help would be greatly appreciated.