Description:
The server works well for 1h and then crash (Windows 10 service is down and I manually restart service and run again normnally for 1-2 hours)
similar bug here - https://bugs.mysql.com/bug.php?id=72264
2018-09-06T19:00:22.671971Z 4 [ERROR] InnoDB: Operating system error number 21 in a file operation.
2018-09-06T19:00:22.672884Z 4 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2018-09-06T19:00:22.672884Z 4 [ERROR] InnoDB: File f:\mysql\tables\compute_pin_teh\photo_resell.ibd: 'Windows aio' returned OS error 121. Cannot continue operation
2018-09-06T19:00:22.673881Z 4 [ERROR] InnoDB: Cannot continue operation.
I executed your the requests on bug 72264
1. check table photo_resell
compute_pin_teh.photo_resell check status OK
2. show table status from compute_pin_teh like 'photo_resell';
photo_resell InnoDB 10 Dynamic 3339504 489 1633681408 0 260702208 7340032 3836352 2018-09-05 19:19:44 2018-09-06 21:30:03 utf8_general_ci
3. show create table photo_resell ;#\G;
result is truncated so I took a similar menu option
Copy to Clipboard Create statement from MySql Workbench
CREATE TABLE `photo_resell` (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`unique_id_supplier` varchar(50) DEFAULT NULL,
`id_supplier` varchar(50) DEFAULT NULL,
`supplier_prefix` varchar(10) DEFAULT NULL,
`id_title` bigint(20) DEFAULT NULL,
`title` text,
`keywords` text,
`description` text,
`id_keywords` bigint(20) DEFAULT NULL,
`downloads` int(11) DEFAULT NULL,
`views` int(11) DEFAULT NULL,
`media_type` varchar(30) DEFAULT NULL,
`width` int(11) DEFAULT NULL,
`height` int(11) DEFAULT NULL,
`sell_url` text,
`medium_thumb` text,
`large_thumb` text,
`refusal` varchar(20) DEFAULT NULL,
`is_indexed_title` tinyint(4) DEFAULT NULL,
`is_indexed_description` tinyint(4) DEFAULT NULL,
`relevance` tinyint(4) DEFAULT '0',
PRIMARY KEY (`id`),
UNIQUE KEY `unique_id_supplier` (`unique_id_supplier`),
KEY `group_key` (`id_keywords`)
) ENGINE=InnoDB AUTO_INCREMENT=3836352 DEFAULT CHARSET=utf8 DATA DIRECTORY='f:/mysql/tables/';
!!! DATA DIRECTORY='f:/mysql/tables/' is a SanDisk SSD 2TB NTFS 4k cluster
(most of the tables are on c: and the 3 large ones > 1Gb on external SSD)
I will come back with more requests that I found on the previous bug
How to repeat:
If I run my java program that writes a lot of lines in this table it crush again (I just insert lines, reading and updating is in a separate procedure that execute in another day)
