【mysql案例】datadir所在分区空间不足导致无法查看表

#datadir所在分区空间不足导致无法查看表

120221 04:49:54 mysqld_safe Starting mysqld daemon with databases from /opt/mysql
120221  4:49:54 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
120221  4:49:54 [Note] Plugin 'FEDERATED' is disabled.
120221  4:49:54 InnoDB: The InnoDB memory heap is disabled
120221  4:49:54 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
120221  4:49:54 InnoDB: Compressed tables use zlib 1.2.3
120221  4:49:54 InnoDB: Using Linux native AIO
120221  4:49:54 InnoDB: Initializing buffer pool, size = 128.0M
120221  4:49:54 InnoDB: Completed initialization of buffer pool
InnoDB: Error: auto-extending data file ./ibdata1 is of a different size
InnoDB: 15360 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 65536 pages, max 0 (relevant if non-zero) pages!
120221  4:49:54 InnoDB: Could not open or create data files.
120221  4:49:54 InnoDB: If you tried to add new data files, and it failed here,
120221  4:49:54 InnoDB: you should now edit innodb_data_file_path in my.cnf back
120221  4:49:54 InnoDB: to what it was, and remove the new ibdata files InnoDB created
120221  4:49:54 InnoDB: in this failed attempt. InnoDB only wrote those files full of
120221  4:49:54 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
120221  4:49:54 InnoDB: remove old data files which contain your precious data!
120221  4:49:54 [ERROR] Plugin 'InnoDB' init function returned error.
120221  4:49:54 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
/usr/sbin/mysqld: Error writing file './slow_query.log' (Errcode: 28)
120221  4:49:54 [ERROR] Could not use slow_query.log for logging (error 28). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
120221  4:49:54 [ERROR] Unknown/unsupported storage engine: INNODB
120221  4:49:54 [ERROR] Aborting


120221  4:49:54 [Note] /usr/sbin/mysqld: Shutdown complete


120221 04:49:54 mysqld_safe mysqld from pid file /opt/mysql/jsunsa.pid ended
120221 04:52:22 mysqld_safe Starting mysqld daemon with databases from /opt/mysql
120221  4:52:22 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
120221  4:52:22 [Note] Plugin 'FEDERATED' is disabled.
120221  4:52:22 InnoDB: The InnoDB memory heap is disabled
120221  4:52:22 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
120221  4:52:22 InnoDB: Compressed tables use zlib 1.2.3
120221  4:52:22 InnoDB: Using Linux native AIO
120221  4:52:22 InnoDB: Initializing buffer pool, size = 128.0M
120221  4:52:22 InnoDB: Completed initialization of buffer pool
120221  4:52:23  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 256 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB:120221  4:52:23  InnoDB: Error: Write to file ./ib_logfile0 failed at offset 0 0.
InnoDB: 1048576 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 quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: Error in creating ./ib_logfile0: probably out of disk space
120221  4:52:23 [ERROR] Plugin 'InnoDB' init function returned error.
120221  4:52:23 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
/usr/sbin/mysqld: Error writing file './slow_query.log' (Errcode: 28)
120221  4:52:23 [ERROR] Could not use slow_query.log for logging (error 28). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
1120221 04:52:23 mysqld_safe mysqld from pid file /opt/mysql/jsunsa.pid ended