InnoDB: Error number 5 means 'Input/output error'. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Check that your OS and file system support files of this size. InnoDB: 65536 bytes should have been written, only 0 were written. \localtest\asset_type_drive_forces.ibd failed at offset 0 0. When I loaded the script with just the CREATE TABLE statements (~840 tables), a few tables gave errors:ĮRROR 1005 (HY000) at line 41: Can't create table 'localtest.asset_type_drive_forces' (errno: 135)ġ10822 16:09:29 InnoDB: Error: Write to file. Then I did a mysqldump from my production db, and tried to load it on my test db. 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. I loaded a mysqldump from my old production machine (MySQL 4.1, 32-bit, Windows) and it loaded fine. ![]() * Windows 7 Professional, version 6.1, Build 7601: Service Pack 1) I recently setup a system that will become my development workstation: I'm getting errors on CREATE TALBE and INSERT from a mysqldump, where the error appears to be coming from Windows AIO.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |