×

Loading...
Ad by
  • 予人玫瑰,手有余香:加拿大新天地工作移民诚聘求职顾问&行业导师!
Ad by
  • 予人玫瑰,手有余香:加拿大新天地工作移民诚聘求职顾问&行业导师!

查了log没有?比如我那里的log在/usr/local/var/H50.err

本文发表在 rolia.net 枫下论坛InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 9
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 9
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060301 18:42:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 48309.
InnoDB: Doing recovery: scanned up to log sequence number 0 48309
InnoDB: Last MySQL binlog file position 0 79, file name ./H50-bin.000024
060301 18:42:03 InnoDB: Flushing modified pages from the buffer pool...
060301 18:42:03 InnoDB: Started; log sequence number 0 48309
/usr/local/libexec/mysqld: ready for connections.
Version: '4.1.14' socket: '/tmp/mysql.sock' port: 3306 Source distribution更多精彩文章及讨论,请光临枫下论坛 rolia.net
Report

Replies, comments and Discussions:

  • 工作学习 / 专业技术讨论 / 这里有熟悉mysql的大侠吗?我的mysql database 每天零晨的时候必会hang,一直找不出原因,请帮忙诊断一下,多谢!
    • 查了log没有?比如我那里的log在/usr/local/var/H50.err
      本文发表在 rolia.net 枫下论坛InnoDB: Crash recovery may have failed for some .ibd files!
      InnoDB: cannot read directory ., error 9
      InnoDB: Error: os_file_readdir_next_file() returned -1 in
      InnoDB: directory .
      InnoDB: Crash recovery may have failed for some .ibd files!
      InnoDB: cannot read directory ., error 9
      InnoDB: Error: os_file_readdir_next_file() returned -1 in
      InnoDB: directory .
      InnoDB: Crash recovery may have failed for some .ibd files!
      InnoDB: Restoring possible half-written data pages from the doublewrite
      InnoDB: buffer...
      060301 18:42:03 InnoDB: Starting log scan based on checkpoint at
      InnoDB: log sequence number 0 48309.
      InnoDB: Doing recovery: scanned up to log sequence number 0 48309
      InnoDB: Last MySQL binlog file position 0 79, file name ./H50-bin.000024
      060301 18:42:03 InnoDB: Flushing modified pages from the buffer pool...
      060301 18:42:03 InnoDB: Started; log sequence number 0 48309
      /usr/local/libexec/mysqld: ready for connections.
      Version: '4.1.14' socket: '/tmp/mysql.sock' port: 3306 Source distribution更多精彩文章及讨论,请光临枫下论坛 rolia.net
      • 查过了,log里没有任何可疑之处。非常之奇怪。
        • 操作系统是什么
          如果是Unix 先查crontab -l, at -l,找那个时间点运行的可疑程序。

          找不到了安装个24小时监视系统的工具。比如AIX可以用nmon,Windows可以用Performance检测工具。 重点关注内存利用率?
          • Freebsd 5.2.1, cron job 查过了,没有任何job相关,内存不应该啊,这个机器内存超过4G. 唉,这个问题真是困扰好久了。不知道mysql 内部有没有什么debug command?
            • 把SERVER TIME调到凌晨,调!