I read the following question that has relevance, but the replies didn\'t satify me: MySQL: #126 - Incorrect key file for table
When runn
If your /tmp
mount on a linux filesystem is mounted as overflow, often sized at 1MB, ie
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.9G 12K 7.9G 1% /dev
tmpfs 1.6G 348K 1.6G 1% /run
/dev/xvda1 493G 6.9G 466G 2% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 7.9G 0 7.9G 0% /run/shm
none 100M 0 100M 0% /run/user
overflow 1.0M 4.0K 1020K 1% /tmp <------
this is likely due to you not specifying /tmp
as its own partition and your root filesystem filled up and /tmp
was remounted as a fallback.
I ran into this issue after running out of space on an EC2 volume. Once I resized the volume, I ran into the /tmp
overflow partition filling up while executing a complicated view.
sudo umount -l /tmp
Note: -l
will lazily unmount the disk.