boro
V2EX  ›  问与答

XAMMP mysql 无法再次启动 求大神给解决办法

  •  
  •   boro · Mar 4, 2014 · 3637 views
    This topic created in 4477 days ago, the information mentioned may be changed or developed.
    电脑突然死机,XAMMP的mysql 无法启动,错误日志如下,求解决办法。谢谢!

    140303 1:09:50 [Note] Plugin 'FEDERATED' is disabled.
    140303 1:09:50 InnoDB: The InnoDB memory heap is disabled
    140303 1:09:50 InnoDB: Mutexes and rw_locks use Windows interlocked functions
    140303 1:09:50 InnoDB: Compressed tables use zlib 1.2.3
    140303 1:09:50 InnoDB: Initializing buffer pool, size = 16.0M
    140303 1:09:50 InnoDB: Completed initialization of buffer pool
    140303 1:09:50 InnoDB: highest supported file format is Barracuda.
    InnoDB: Log scan progressed past the checkpoint lsn 59971167
    140303 1:09:50 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 59972515
    140303 1:09:57 InnoDB: Operating system error number 23 in a file operation.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    InnoDB: File name D:\xampp\mysql\data\ibdata1
    InnoDB: File operation call: 'Windows aio'.
    InnoDB: Cannot continue operation.
    140303 1:10:00 [Note] Plugin 'FEDERATED' is disabled.
    140303 1:10:00 InnoDB: The InnoDB memory heap is disabled
    140303 1:10:00 InnoDB: Mutexes and rw_locks use Windows interlocked functions
    140303 1:10:00 InnoDB: Compressed tables use zlib 1.2.3
    140303 1:10:00 InnoDB: Initializing buffer pool, size = 16.0M
    140303 1:10:00 InnoDB: Completed initialization of buffer pool
    140303 1:10:00 InnoDB: highest supported file format is Barracuda.
    InnoDB: Log scan progressed past the checkpoint lsn 59971167
    140303 1:10:00 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 59972515
    140303 1:10:07 InnoDB: Operating system error number 23 in a file operation.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    InnoDB: File name D:\xampp\mysql\data\ibdata1
    InnoDB: File operation call: 'Windows aio'.
    InnoDB: Cannot continue operation.
    2 replies    1970-01-01 08:00:00 +08:00
    lululau
        1
    lululau  
       Mar 4, 2014   ❤️ 1
    系统打开文件数量太多,重启下机器试试
    boro
        2
    boro  
    OP
       Apr 2, 2014
    重启也无法解决
    About   ·   Help   ·   Advertise   ·   Blog   ·   API   ·   FAQ   ·   Solana   ·   2922 Online   Highest 6679   ·     Select Language
    创意工作者们的社区
    World is powered by solitude
    VERSION: 3.9.8.5 · 34ms · UTC 13:37 · PVG 21:37 · LAX 06:37 · JFK 09:37
    ♥ Do have faith in what you're doing.