账号密码登录
微信安全登录
微信扫描二维码登录

登录后绑定QQ、微信即可实现信息互通

手机验证码登录
找回密码返回
邮箱找回 手机找回
注册账号返回
其他登录方式
分享
  • 收藏
    X
    win7下DockerToolbox中的MySQL启动失败-Cannot continue oper ation?
    57
    0

    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!
    0
    打赏
    收藏
    点击回答
        全部回答
    • 0
    • 隔壁姐姐 普通会员 1楼
      502 Bad Gateway

      502 Bad Gateway


      nginx
    更多回答
    扫一扫访问手机版
    • 回到顶部
    • 回到顶部