win7 下 DockerToolbox 中的 MySQL 启动失败-[ERROR] InnoDB: Cannot continue oper ation.

docker-compose.yml 编排文件在 linux 和 win10 运行是正常, win7 中的 DockerToolbox 就出现下面问题.

处理了现象一后, 又跑出现象二. 囧~

错误现象一

mysql_1     | 2018-01-30T09:01:32.534590Z 0 [ERROR] InnoDB: File ./ib_logfile0:
'aio write' returned OS error 122. Cannot continue operation
mysql_1     | 2018-01-30T09:01:32.534632Z 0 [ERROR] InnoDB: Cannot continue oper
ation.

讨论记录 用了里面的脚本又出现下面的错误.

错误现象二

mysql5.6_1  | 2018-01-30 08:43:06 18 [Warning] InnoDB: Doublewrite does not have
 page_no=0 of space: 0
mysql5.6_1  | 2018-01-30 08:43:06 18 [ERROR] InnoDB: space header page consists
of zero bytes in data file ./ibdata1
mysql5.6_1  | 2018-01-30 08:43:06 18 [ERROR] InnoDB: Could not open or create th
e system tablespace. If you tried to add new data files to the system tablespace
, and it failed here, you should now edit innodb_data_file_path in my.cnf back t
o what it was, and remove the new ibdata files InnoDB created in this failed att
empt. InnoDB only wrote those files full of zeros, but did not yet use them in a
ny way. But be careful: do not remove old data files which contain your precious
 data!