mysql 錯誤- 磁碟空間不足，

標籤：style   blog   color   io   os   ar   for   strong   sp   

mysql 磁碟空間不足錯誤

　　磁碟空間滿了， 寫不進去了。

 

141020 09:45:24 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql-5.6.20/data2014-10-20 09:45:24 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).2014-10-20 09:45:24 1606 [Note] Plugin ‘FEDERATED‘ is disabled.2014-10-20 09:45:24 1606 [Note] InnoDB: Using atomics to ref count buffer pool pages2014-10-20 09:45:24 1606 [Note] InnoDB: The InnoDB memory heap is disabled2014-10-20 09:45:24 1606 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2014-10-20 09:45:24 1606 [Note] InnoDB: Memory barrier is not used2014-10-20 09:45:24 1606 [Note] InnoDB: Compressed tables use zlib 1.2.32014-10-20 09:45:24 1606 [Note] InnoDB: Using CPU crc32 instructions2014-10-20 09:45:24 1606 [Note] InnoDB: Initializing buffer pool, size = 128.0M2014-10-20 09:45:24 1606 [Note] InnoDB: Completed initialization of buffer pool2014-10-20 09:45:24 1606 [Note] InnoDB: Highest supported file format is Barracuda.2014-10-20 09:45:24 1606 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5101000072014-10-20 09:45:24 1606 [Note] InnoDB: Database was not shutdown normally!2014-10-20 09:45:24 1606 [Note] InnoDB: Starting crash recovery.2014-10-20 09:45:24 1606 [Note] InnoDB: Reading tablespace information from the .ibd files...2014-10-20 09:45:24 1606 [Note] InnoDB: Restoring possible half-written data pages 2014-10-20 09:45:24 1606 [Note] InnoDB: from the doublewrite buffer...InnoDB: Doing recovery: scanned up to log sequence number 510107962InnoDB: Transaction 3310511 was in the XA prepared state.InnoDB: Transaction 3310511 was in the XA prepared state.InnoDB: Transaction 3310547 was in the XA prepared state.InnoDB: Transaction 3310547 was in the XA prepared state.InnoDB: Transaction 3308073 was in the XA prepared state.InnoDB: Transaction 3308073 was in the XA prepared state.InnoDB: Transaction 3311321 was in the XA prepared state.InnoDB: 4 transaction(s) which must be rolled back or cleaned upInnoDB: in total 0 row operations to undoInnoDB: Trx id counter is 33169922014-10-20 09:45:24 1606 [Note] InnoDB: Starting an apply batch of log records to the database...InnoDB: Progress in percent: 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completedInnoDB: Last MySQL binlog file position 0 518283216, file name binlog.000003InnoDB: Starting in background the rollback of uncommitted transactions2014-10-20 09:45:25 7f1414c46700  InnoDB: Rollback of non-prepared transactions completed2014-10-20 09:45:25 1606 [Note] InnoDB: 128 rollback segment(s) are active.2014-10-20 09:45:25 1606 [Note] InnoDB: 5.6.20 started; log sequence number 5101079622014-10-20 09:45:25 7f143e37a720  InnoDB: Starting recovery for XA transactions...2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3311321 in prepared state after recovery2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 1 rows2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3310547 in prepared state after recovery2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 4 rows2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3310511 in prepared state after recovery2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 4 rows2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3308073 in prepared state after recovery2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 5 rows2014-10-20 09:45:25 7f143e37a720  InnoDB: 4 transactions in prepared state after recovery2014-10-20 09:45:25 1606 [Note] Found 4 prepared transaction(s) in InnoDB2014-10-20 09:45:25 7f143e37a720 InnoDB: Error: Write to file ./test_szd/T_SD_AUCTION.ibd failed at offset 376832.InnoDB: 16384 bytes should have been written, only -1 were written.InnoDB: Operating system error number 28.InnoDB: Check that your OS and file system support files of this size.InnoDB: Check also that the disk is not full or a disk 141020 09:45:31 mysqld_safe mysqld from pid file /alidata/server/mysql-5.6.20/data/iZ23lt92evyZ.pid ended

 

mysql 錯誤- 磁碟空間不足，