mysql 错误- 磁盘空间不足，

mysql 磁盘空间不足错误

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

 :: mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql-5.6./data
-- ::  [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
-- ::  [Note] Plugin 'FEDERATED' is disabled.
-- ::  [Note] InnoDB: Using atomics to ref count buffer pool pages
-- ::  [Note] InnoDB: The InnoDB memory heap is disabled
-- ::  [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
-- ::  [Note] InnoDB: Memory barrier is not used
-- ::  [Note] InnoDB: Compressed tables use zlib 1.2.
-- ::  [Note] InnoDB: Using CPU crc32 instructions
-- ::  [Note] InnoDB: Initializing buffer pool, size = 128.0M
-- ::  [Note] InnoDB: Completed initialization of buffer pool
-- ::  [Note] InnoDB: Highest supported file format is Barracuda.
-- ::  [Note] InnoDB: Log scan progressed past the checkpoint lsn
-- ::  [Note] InnoDB: Database was not shutdown normally!
-- ::  [Note] InnoDB: Starting crash recovery.
-- ::  [Note] InnoDB: Reading tablespace information from the .ibd files...
-- ::  [Note] InnoDB: Restoring possible half-written data pages
-- ::  [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB: Transaction  was in the XA prepared state.
InnoDB:  transaction(s) which must be rolled back or cleaned up
InnoDB: in total  row operations to undo
InnoDB: Trx id counter is
-- ::  [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent:
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position  , file name binlog.
InnoDB: Starting in background the rollback of uncommitted transactions
-- :: 7f1414c46700  InnoDB: Rollback of non-prepared transactions completed
-- ::  [Note] InnoDB:  rollback segment(s) are active.
-- ::  [Note] InnoDB: 5.6. started; log sequence number
-- :: 7f143e37a720  InnoDB: Starting recovery for XA transactions...
-- :: 7f143e37a720  InnoDB: Transaction  in prepared state after recovery
-- :: 7f143e37a720  InnoDB: Transaction contains changes to  rows
-- :: 7f143e37a720  InnoDB: Transaction  in prepared state after recovery
-- :: 7f143e37a720  InnoDB: Transaction contains changes to  rows
-- :: 7f143e37a720  InnoDB: Transaction  in prepared state after recovery
-- :: 7f143e37a720  InnoDB: Transaction contains changes to  rows
-- :: 7f143e37a720  InnoDB: Transaction  in prepared state after recovery
-- :: 7f143e37a720  InnoDB: Transaction contains changes to  rows
-- :: 7f143e37a720  InnoDB:  transactions in prepared state after recovery
-- ::  [Note] Found  prepared transaction(s) in InnoDB
-- :: 7f143e37a720 InnoDB: Error: Write to file ./test_szd/T_SD_AUCTION.ibd failed at offset .
InnoDB:  bytes should have been written, only - were written.
InnoDB: Operating system error number .
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