Ошибка записи write 28 no space left on device

I have the following error with one of our web applications —

Query3 failed: Error writing file '/tmp/MY1fnqpm' (Errcode: 28) ... INSERT MailList... (removed the rest of the query for security reasons)

Any ideas — is this some hard disk space issue on my server?

We have experienced similar issue, and the problem was MySQL used /tmp directory for its needs (it’s default configuration). And /tmp was located on its own partition, that had too few space for big MySQL requests.

For more details take a look for this answer:
https://stackoverflow.com/a/3716778/994302

This error occurs when you don’t have enough space in the partition. Usually MYSQL uses /tmp on linux servers. This may happen with some queries because the lookup was either returning a lot of data, or possibly even just sifting through a lot of data creating big temp files.

Edit your /etc/mysql/my.cnf

tmpdir = /your/new/dir

e.g

tmpdir = /var/tmp

Should be allocated with more space than /tmp that is usually in it’s own partition.

answered Feb 28, 2018 at 5:09

I had this same error and the problem was simply not enough space on my virtual machine. I deleted some unnecessary files and it started working again.

my
memory/disk space allocation looked something like this

df -h
Filesystem               Size  Used Avail Use% Mounted on
/dev/mapper/centos-root   37G   37G  127M 100% /
...

answered Dec 27, 2018 at 5:41

For those like me who don’t have a full disk or full inodes and that are using MySQL 8, you should take a look at your /var/lib/mysql directory to check if there is some large binlog.XXXXXX files.

It was the case for me and it prevented a query to be executed until the end because it seemed like this query was generating a large binlog file.

I just had to turn off the logbin generation by adding this parameter in /etc/mysql/mysql.conf.d/mysqld.cnf :

disable_log_bin

Then restart mysql service :

service mysql restart

After that i didn’t have the «No space left on device» error anymore!

answered Oct 6, 2022 at 12:27

You can also try using this line if the other doesn’t work:

du -sh /var/lib/mysql/database_Name

You may also want to check with your host and see how big they allow your databases to be.

answered Feb 4, 2015 at 23:46

answered May 11, 2017 at 9:47

Today. I have same problem… my solution:

1) check inode: df -i
I saw:

root@vm22433:/etc/mysql# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 124696 304 124392 1% /dev
tmpfs 127514 452 127062 1% /run
/dev/vda1 1969920 1969920 0 100% /
tmpfs 127514 1 127513 1% /dev/shm
tmpfs 127514 3 127511 1% /run/lock
tmpfs 127514 15 127499 1% /sys/fs/cgroup
tmpfs 127514 12 127502 1% /run/user/1002

2) I began to look what folders use the maximum number of inods:

 for i in /*; do echo $i; find $i |wc -l; done

soon I found in /home/tomnolane/tmp folder, which contained a huge number of files.

3) I removed /home/tomnolane/tmp folder
PROFIT.

4) checked:

Filesystem      Inodes  IUsed   IFree IUse% Mounted on
udev            124696    304  124392    1% /dev
tmpfs           127514    454  127060    1% /run
/dev/vda1      1969920 450857 1519063   23% /
tmpfs           127514      1  127513    1% /dev/shm
tmpfs           127514      3  127511    1% /run/lock
tmpfs           127514     15  127499    1% /sys/fs/cgroup
tmpfs           127514     12  127502    1% /run/user/1002

it’s ok.

5) restart mysql service — it’s ok!!!!

answered Dec 1, 2018 at 22:05

I had the same problem and after little research found that the snap directory was occupying most of the space. So executed following command to get rid of it:

sudo apt autoremove --purge snapd

After that ran following command to get rid of useless/dev/loop mounts:

`sudo apt purge snapd ubuntu-core-launcher squashfs-tools`

After that ran following command to restart mysql:

sudo service mysql restart

It worked for me!

answered Jan 22, 2022 at 22:15

How to resolve the error when I run the apt-get update command? I have more than 100 GB left on my mac device

 Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)

Commands that I executed to check the free space.

user:~/.docker$df -h
Filesystem      Size   Used  Avail Capacity iused               ifree %iused  Mounted on
/dev/disk1s1   233Gi   93Gi  136Gi    41% 1479561 9223372036853296246    0%   /
devfs          187Ki  187Ki    0Bi   100%     648                   0  100%   /dev
/dev/disk1s4   233Gi  4.0Gi  136Gi     3%       4 9223372036854775803    0%   /private/var/vm
map -hosts       0Bi    0Bi    0Bi   100%       0                   0  100%   /net
map auto_home    0Bi    0Bi    0Bi   100%       0                   0  100%   /home

user:~/.docker$cat daemon.json 
{
  "debug" : true,
  "experimental" : false
}

user:~/.docker$cat config.json 
{
  "credsStore" : "desktop",
  "auths" : {

  },
  "stackOrchestrator" : "swarm",
  "experimental" : "disabled"
}

asked Nov 26, 2019 at 23:35

I configured the local environment docker to reuse the docker daemon inside the minikube instance.

There were many docker images listed when I used docker images command

Removed all the docker images using docker rmi -f imageName

After removing all the docker images, I was able to get some space and the Debian issue is resolved

answered Dec 4, 2019 at 22:34

How to resolve the error when I run the apt-get update command? I have more than 100 GB left on my mac device

 Error writing to output file - write (28: No space left on device) Error writing to file - write (28: No space left on device)

Commands that I executed to check the free space.

user:~/.docker$df -h
Filesystem      Size   Used  Avail Capacity iused               ifree %iused  Mounted on
/dev/disk1s1   233Gi   93Gi  136Gi    41% 1479561 9223372036853296246    0%   /
devfs          187Ki  187Ki    0Bi   100%     648                   0  100%   /dev
/dev/disk1s4   233Gi  4.0Gi  136Gi     3%       4 9223372036854775803    0%   /private/var/vm
map -hosts       0Bi    0Bi    0Bi   100%       0                   0  100%   /net
map auto_home    0Bi    0Bi    0Bi   100%       0                   0  100%   /home

user:~/.docker$cat daemon.json 
{
  "debug" : true,
  "experimental" : false
}

user:~/.docker$cat config.json 
{
  "credsStore" : "desktop",
  "auths" : {

  },
  "stackOrchestrator" : "swarm",
  "experimental" : "disabled"
}

asked Nov 26, 2019 at 23:35

I configured the local environment docker to reuse the docker daemon inside the minikube instance.

There were many docker images listed when I used docker images command

Removed all the docker images using docker rmi -f imageName

After removing all the docker images, I was able to get some space and the Debian issue is resolved

answered Dec 4, 2019 at 22:34

Я проверил, есть ли у меня место на жестком диске.

Я очень новичок в Linux, и я пытаюсь установить обновления на своем сервере.

Когда я выполняю

ubuntu@ip-xxxxxxxxxxxx:~$ sudo apt-get -f install


, я сразу получаю этот ответ

Reading package lists... Error!
E: Write error - write (28: No space left on device)


Вторая строка повторяется около 60 раз.

Когда я запускаю sudo df — h, я получаю

Filesystem Size Used Avail Use% Mounted on
udev 2.0G 4.0K 2.0G 1% /dev
tmpfs 396M 348K 395M 1% /run
/dev/xvda1 24G 14G 9.0G 61% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 2.0G 0 2.0G 0% /run/shm
none 100M 0 100M 0% /run/user
overflow 1.0M 1.0M 0 100% /tmp


. Я понимаю, что мой диск имеет 9.0G влево, но я не знаю, что делают остальные диски или файловые системы?

Это экземпляр AWS Ubuntu, который я недавно увеличил в размерах, и у меня есть ощущение, что я пропускаю шаг, чтобы использовать эти 9Gb?

sudo cp /etc/fstab /etc/fstab.bak
sudo nano /etc/fstab

ответ дан Katu
22 May 2018 в 16:04

поделиться

ответ дан Katu
18 July 2018 в 02:57

поделиться

ответ дан Katu
24 July 2018 в 17:42

поделиться