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

Question

I get this error when trying to start MySQL: The partition with /var/lib/mysql is too full!

Here is the output of df -h:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       455G   77G  356G  18% /
none            4,0K     0  4,0K   0% /sys/fs/cgroup
udev            1,9G  4,0K  1,9G   1% /dev
tmpfs           387M  1,3M  386M   1% /run
none            5,0M     0  5,0M   0% /run/lock
none            1,9G  1,2M  1,9G   1% /run/shm
none            100M   28K  100M   1% /run/user

This shows that the partition is nowhere near full.

I'm sorry if this is a dumb question, but which one is the correct log: ib_logfile0 or ib_logfile1? — rocketgear, Jun 13 '14 at 19:21
There seem to be no such files in /var/lib/mysql. I've even reinstalled mysql-server, but nothing changed. — rocketgear, Jun 13 '14 at 19:36
i got same problem on virtual machine, but here i forgot to expand the disk from 8gb to 2tb so this post resorve my problem, thanks :) — ParisNakitaKejser, Mar 04 '15 at 09:56

score 13 · Answer 1 · answered Jun 14 '14 at 09:33

13

I finally fixed it by running sudo /etc/init.d/mysql start. I just had to insert sudo in front of the command.

answered Jun 14 '14 at 09:33

rocketgear

409
1
3
7

1

How can this fix the issue? The OP got this error when trying to start MySQL, and this command do nothing to help. – Paul Lo Feb 05 '15 at 06:30
@PaulLo it really helps. I forgot to add sudo. – shukshin.ivan Jan 14 '16 at 14:54
4

I don't understand how this got 8 upvotes. – Parth Thakkar Jun 12 '16 at 12:56
This fixed it for me. I don't know why this works but it does. I was getting the error saying the partition is full when trying to start mysql. I ran the command using sudo and mysql started just fine. – Gavin Aug 12 '16 at 19:23
Wow, sudo service mysql restart was saying everything was good, but running this command actually fixed the problem. I don't get the difference ... – George Dimitriadis Sep 23 '17 at 15:16

score 6 · Answer 2 · edited Sep 17 '14 at 08:29

6

try this:

sudo service mysql stop
sudo service mysql start

edited Sep 17 '14 at 08:29

Parto

15,325
24
86
117

answered Sep 17 '14 at 08:20

Steve Dörre

61

2

i had the same problem 'The partition with /var/lib/mysql is too full!' and i fixed it this way! – Steve Dörre Sep 17 '14 at 09:23
@KasiyA yes it is an answer to the question (but it is the same as the answer given by rocketgear himself) (stop/start will fix this notice) – Rinzwind Sep 17 '14 at 09:45
@Rinzwind uhh. sorry – αғsнιη Sep 17 '14 at 11:13
in my case sudo /etc/init.d/mysql start doesn't work.... – Steve Dörre Sep 17 '14 at 17:34

score 3 · Answer 3 · answered Apr 27 '15 at 21:11

In my case the error resulted of changing the ip address on the server.

cat /var/log/mysql/error.log

150427 23:01:08 InnoDB: 5.5.43 started; log sequence number 11731761
150427 23:01:08 [Note] Server hostname (bind-address): '192.168.1.234'; port: 3306
150427 23:01:08 [Note]   - '192.168.1.234' resolves to '192.168.1.234';
150427 23:01:08 [Note] Server socket created on IP: '192.168.1.234'.
150427 23:01:08 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address
150427 23:01:08 [ERROR] Do you already have another mysqld server running on port: 3306 ?
150427 23:01:08 [ERROR] Aborting

changing the

 bind-address

in

 /etc/mysql/my.cnf

to the current ip and restarting the server

sudo /etc/init.d/mysql start

solved the problem

score 2 · Answer 4 · edited Apr 13 '17 at 12:14

There are two possible problems with Mysql package:

Really a space problem:

Many distributions have their /var directory in the original root partition which is not made big enough by default to hold real-life data. They usually create separate partition for /usr with tons of space

Check this and you will get full details and your answer

https://serverfault.com/questions/256729/error-the-partition-with-var-lib-mysql-is-too-full
It is a bug which might not have been fixed and to fix it follow this article:

https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.0/+bug/118523

score 1 · Answer 5 · answered Nov 26 '14 at 15:59

I have faced same issue, in my case there is another mysql service was running

$ ps -aux | grep mysql
mysql     7241  0.0  5.1 562600 52812 ?        Ssl  13:36   0:02 /usr/sbin/mysql
ubuntu   13580  0.0  0.0  10468   916 pts/0    S+   15:50   0:00 grep --color=au

$ sudo kill  7241

Then I started mysql.

$ sudo /etc/init.d/mysql start
* Starting MySQL database server mysqld                                 [ OK ]

Pablo Bianchi · Answer 6 · 2023-07-03T11:39:06.557

0

In my case the problem was that /var was full:

$ df -h  # More info with du -h /var | sort -hr | head -10
...
/dev/sda3       2.7G  2.7G     0 100% /var

So I just used ncdu (another nice tool is dust) to check what was taking so much space:

sudo ncdu /var

Delete some useless stuff with d, restarted

sudo systemctl restart mysql.service

And voilà, everything working now.

What to delete? Each case should be analyzed carefully. Start with sudo apt autoremove, snap stuff, rotate your logs and maybe remove old stuff/backups: /var/crash, /var/cache, /var/tmp…

edited Jul 03 '23 at 11:39

answered Jan 31 '19 at 06:06

Pablo Bianchi

15,657

Can you provide some example of useless stuff? – Dimitrios Desyllas Jul 03 '23 at 11:19
@DimitriosDesyllas I added some examples to the post :) – Pablo Bianchi Jul 03 '23 at 11:39

score 0 · Answer 7 · answered Nov 18 '21 at 16:12

0

In my case, it was just the date was wrong. Somehow, after a blade failure (it is a VM), the OS started up with a wring date. Once i changed to the corrent date, mysql started correctly

answered Nov 18 '21 at 16:12

Alejandro Gonzalez

1

score 0 · Answer 8 · edited Jan 21 '17 at 05:27

In the partition /var there are several directories that accumulate many files which can fill up the partition.

In my case logs are saved in /var/logs filling up /var prevented me from starting mysql.

I deleted some of those old logs and that solved my problem. If you do not have log rotation it is better that you try acerlo since if you do not have this process the logs can add up to many GB in a single file.

score -1 · Answer 9 · answered Jun 13 '14 at 19:39

-1

Run the command sudo apt-get --reinstall install mysql-server to re-install MySQL. It will re-create the missing directories and allow you to start the server again.

answered Jun 13 '14 at 19:39

Bert

3,225
1
14
12

This is what I got: dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.5; however: Package mysql-server-5.5 is not configured yet. How do I use --configure? – rocketgear Jun 13 '14 at 19:51

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

9 Answers9

Linked