Inability to view table problems caused by insufficient partition space in DataDir

Source: Internet
Author: User
Tags deprecated file system mysql linux

Unable to view table due to insufficient partition space in 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 would removed in a future release. 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 at 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

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.

/usr/sbin/mysqld:error writing file './slow_query.log ' (errcode:28)

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/storage/

120221 4:49:54 [ERROR] could not use Slow_query.log for logging (Error 28). Turning logging off for the whole duration the MySQL server process. To turn it 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 would removed in a future release. 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 at offset 0 0.

innodb:1048576 bytes should have been written, only-1 were.

Innodb:operating system error number 28.

Innodb:check that your OS and file system support files of this size.

Innodb:check also that this disk is not full or a disk quota exceeded.

Innodb:error number means ' No spaces 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 spaces

120221 4:52:23 [ERROR] Plugin ' InnoDB ' init function returned ERROR.

120221 4:52:23 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE.

/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 the MySQL server process. To turn it 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

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.