C
C#8mo ago
3R1C

❔ MySQL server issue (Error 28)

I'll prefix this with a few things: - I'm not driven with Ubuntu or other unix based systems. - The MySQL server in question runs fine with other programs, leading me to believe this might be a memory issue from the scale of the process.
Unhandled exception. MySqlConnector.MySqlException (0x80004005): Error writing file '/tmp/MYfd=73' (OS errno 28 - No space left on device)
Unhandled exception. MySqlConnector.MySqlException (0x80004005): Error writing file '/tmp/MYfd=73' (OS errno 28 - No space left on device)
Here's what I've checked. inodes:
ubuntu@<hostname>:<filepath>$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
tmpfs 2033848 1089 2032759 1% /run
/dev/md2 121995264 93626 121901638 1% /
tmpfs 2033848 3 2033845 1% /dev/shm
tmpfs 2033848 3 2033845 1% /run/lock
/dev/md1 65408 596 64812 1% /boot
tmpfs 406769 28 406741 1% /run/user/1000
ubuntu@<hostname>:<filepath>$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
tmpfs 2033848 1089 2032759 1% /run
/dev/md2 121995264 93626 121901638 1% /
tmpfs 2033848 3 2033845 1% /dev/shm
tmpfs 2033848 3 2033845 1% /run/lock
/dev/md1 65408 596 64812 1% /boot
tmpfs 406769 28 406741 1% /run/user/1000
So that does not seem to be an issue. I even went into mysqld.cnf and changed the tmp path to
tmpdir = /var/tmp/
tmpdir = /var/tmp/
Filesystem space does not seem to be an issue either:
ubuntu@<hostname>:<filepath> df -h --total
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.6G 1.4M 1.6G 1% /run
/dev/md2 1.8T 39G 1.7T 3% /
tmpfs 7.8G 8.0K 7.8G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/md1 988M 227M 695M 25% /boot
tmpfs 1.6G 4.0K 1.6G 1% /run/user/1000
total 1.8T 39G 1.7T 3% -
ubuntu@<hostname>:<filepath> df -h --total
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.6G 1.4M 1.6G 1% /run
/dev/md2 1.8T 39G 1.7T 3% /
tmpfs 7.8G 8.0K 7.8G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/md1 988M 227M 695M 25% /boot
tmpfs 1.6G 4.0K 1.6G 1% /run/user/1000
total 1.8T 39G 1.7T 3% -
After some googling it should either be the inodes or filespace, and neither one appears to be the culprit.
3 Replies
3R1C
3R1C8mo ago
Update: I found the reason and it was incredibly silly.
Murten
Murten8mo ago
Nice.
Accord
Accord8mo ago
Was this issue resolved? If so, run /close - otherwise I will mark this as stale and this post will be archived until there is new activity.