記一次測試環境MySQL無法啟動的案例。

歡迎轉載，請註明作者、出處。

作者：張正

blog：http://space.itpub.net/26355921

QQ：176036317

如有疑問，歡迎聯絡。

問題描述：MySQL伺服器重啟後，資料庫例項無法啟動，日誌資訊如下：

InnoDB: Transaction 91AE18A was in the XA prepar140805 13:51:18 mysqld_safe mysqld from pid file /data/mysql6015/mysqld.pid ended
140805 13:52:16 mysqld_safe Starting mysqld daemon with databases from /data/mysql6015/data/
140805 13:52:16 InnoDB: The InnoDB memory heap is disabled
140805 13:52:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140805 13:52:16 InnoDB: Compressed tables use zlib 1.2.3
140805 13:52:17 InnoDB: Initializing buffer pool, size = 1.0G
140805 13:52:18 InnoDB: Completed initialization of buffer pool
140805 13:52:18 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140805 13:52:18 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: Transaction 91ABFEE was in the XA prepared state.
InnoDB: Transaction 91B0DD3 was in the XA prepared state.
InnoDB: Transaction 91ABFF1 was in the XA prepared state.
InnoDB: Transaction 91ACADF was in the XA prepared state.
InnoDB: Transaction 91AC56B was in the XA prepared state.
InnoDB: Transaction 91AC175 was in the XA prepared state.
InnoDB: Transaction 91AE2B4 was in the XA prepared state.
InnoDB: Transaction 91AD1D8 was in the XA prepared state.
InnoDB: Transaction 91AC7ED was in the XA prepared state.
InnoDB: Transaction 91B0D62 was in the XA prepared state.
InnoDB: Transaction 91AC37B was in the XA prepared state.
InnoDB: Transaction 91AF11F was in the XA prepared state.
InnoDB: Transaction 91AC774 was in the XA prepared state.
InnoDB: Transaction 91AE2BE was in the XA prepared state.
InnoDB: Transaction 91AC006 was in the XA prepared state.
InnoDB: Transaction 91ACAF1 was in the XA prepared state.
...............................................................
InnoDB: Transaction 91AE275 was in the XA prepared state.
InnoDB: Transaction 91AD70D was in the XA prepared state.
InnoDB: Transaction 91ACB28 was in the XA prepared state.
InnoDB: Transaction 91AE37D was in the XA prepared state.
InnoDB: Transaction 91AE204 was in the XA prepared state.
InnoDB: Transaction 91AF2E5 was in the XA prepared state.
InnoDB: Transaction 91AD4A2 was in the XA prepared state.
InnoDB: Transaction 91AE18A was in the XA prepar140805 13:53:09 mysqld_safe mysqld from pid file /data/mysql6015/mysqld.pid ended

排查了10分鐘之後，看了一下磁碟，才發現磁碟已滿：

[root@localhost log]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 40G 6.5G 31G 18% /
tmpfs 4.9G 0 4.9G 0% /dev/shm
/dev/sda1 504M 58M 421M 13% /boot
/dev/sdb1 197G 187G 0 100% /data

清理掉磁碟空間後，再次啟動，OK。

各位看到這裡，是不是覺得很無語。。。。

MySQL伺服器異常關閉，重啟後，無法啟動----因為磁碟空間滿

相關文章