mysql 错误- 磁盘空间不足,

mysql 磁盘空间不足错误

  磁盘空间满了, 写不进去了。

 

141020 09:45:24 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql-5.6.20/data
2014-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 pages
2014-10-20 09:45:24 1606 [Note] InnoDB: The InnoDB memory heap is disabled
2014-10-20 09:45:24 1606 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-10-20 09:45:24 1606 [Note] InnoDB: Memory barrier is not used
2014-10-20 09:45:24 1606 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-10-20 09:45:24 1606 [Note] InnoDB: Using CPU crc32 instructions
2014-10-20 09:45:24 1606 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-10-20 09:45:24 1606 [Note] InnoDB: Completed initialization of buffer pool
2014-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 510100007
2014-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 510107962
InnoDB: 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 up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 3316992
2014-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 completed
InnoDB: Last MySQL binlog file position 0 518283216, file name binlog.000003
InnoDB: Starting in background the rollback of uncommitted transactions
2014-10-20 09:45:25 7f1414c46700  InnoDB: Rollback of non-prepared transactions completed
2014-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 510107962
2014-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 recovery
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 1 rows
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3310547 in prepared state after recovery
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 4 rows
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3310511 in prepared state after recovery
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 4 rows
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction 3308073 in prepared state after recovery
2014-10-20 09:45:25 7f143e37a720  InnoDB: Transaction contains changes to 5 rows
2014-10-20 09:45:25 7f143e37a720  InnoDB: 4 transactions in prepared state after recovery
2014-10-20 09:45:25 1606 [Note] Found 4 prepared transaction(s) in InnoDB
2014-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

 

郑重声明:本站内容如果来自互联网及其他传播媒体,其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享,并不代表本站赞同其观点和对其真实性负责,也不构成任何其他建议。