Mysql – ERROR: The partition with /var/lib/thesql is too full!

amazon ec2disk-space-utilizationMySQL

I am running in a problem here I have a linux instance running on EC2. All was working fine till last night. Today morning it showed me some error stating that there was no disk space to write of mysql.

So I tried to stop and start mysql server. Stopping worked fine, but when i start with following command

sudo /etc/init.d/mysql start

It is showing me the error

ERROR: The partition with /var/lib/mysql is too full!

Best Answer

Check your disk space usage.

sudo df -h

You can mount large database to another partition through binding.

bind is a mount option to mount directories inside directories.

Related Solutions

Mysql – Can’t start/stop thesql service

mysqladmin shutdown

should work to shutdown the server.

I see two likely possibilities:

MySQL has a problem and is refusing to shut down for some reason.
The previous admin did something strange. Either modified the init.d script or didn't bother using the Debian packages at all to install MySQL.

What does dpkg --list mysql\* say?

What does /var/log/mysql.err say? Or the other mysql logs?

EDIT:

So mysqladmin shutdown worked?

According to that, the mysql-server package is installed (mysql-server-5.0; the mysql-server package is probably just a stub). So they may have installed over it? Running debsums mysql-server-5.0 might tell you more. dpkg --listfiles mysql-server-5.0 could help, too...

What's actually in /etc/init.d/mysql? I haven't checked that specific version of the package, but it should try to use mysqladmin shutdown ... Maybe you're lucky and they only broke that...

Mysql – Copying /var/lib/thesql files over resulted in InnoDB corruption

Wow, you really did a number on your database there. You can restore by copying over MySQL data files, but it sounds like you used a little too much mallet. The correct way to do it:

Make sure MySQL IS NOT RUNNING on the machine you're trying to restore onto. Quadruple check with ps to make sure nothing of a MySQL-like nature is lurking. Boot into single user mode if you have to. If MySQL is running, you'll hose all sorts of things.
Copy over both the contents of /var/lib/mysql (or wherever your MySQL data is), as well as the my.cnf that your server was using. It is important to ensure that the config is the same when running InnoDB, because (as you noted) otherwise InnoDB doesn't work. (The crucial parameters are your InnoDB log size/count/etc, and file-per-table -- if they're different, you really ain't going nowhere).

When you start things up, especially if you're restoring a machine that died a violent and untimely death, expect the server to take a while to get itself up and running, as it needs to do all sorts of internal consistency checks (the equivalent of an fsck) before it's ready for service.

Best Answer

Related Solutions

Mysql – Can’t start/stop thesql service

Mysql – Copying /var/lib/thesql files over resulted in InnoDB corruption

Related Topic