MySQL Error 28

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Restoring backup to a new MySQL database fail with the following error:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 java.io.IOException: Error writing to the database: Got error 28 from storage engine at com.atlassian.crucible.migration.item.SQLBackup.restore(SQLBackup.java:205) at com.atlassian.crucible.migration.item.SQLBackup$1.restore(SQLBackup.java:169) at com.cenqua.fisheye.ctl.Restore.run(Restore.java:191) at com.cenqua.fisheye.ctl.Restore.main(Restore.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:98) at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41) Caused by: java.sql.SQLException: Got error 28 from storage engine at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)

Cause

MySQL Error 28 means that the database server ran out of disk space or no space left to work in its tmp directory for linux.

Resolution

  1. Increase the disk space on the database server

  2. Restore the backup to a new empty database again

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.