Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I was trying to load some test data and it appears to have killed my entire database. This is one case where it's great to have backups! They were all plain insert queries, probably about a 900 MB file. What could have gone wrong?

When I woke up (I let it run overnight) mysql was not responding at all, prompting a reboot of the server to fix it. Then I got code 28 errors when attempting to list any tables.

Is there something I can use to guard against this in the future?

share|improve this question
code 28 = out of disk space. free some disk space! – Nick Kavadias May 28 '10 at 16:08
Disk space. Ug. The one thing I did not check. – Josh K May 28 '10 at 18:02
up vote 2 down vote accepted

It's important to remember that the data you are loading may be 900mb outside of your RDBMS but may be even more in the database with out compression. You also have to accout for database growth if it does it in chunks and transaction log space. So always be sure you have ample disk space when doing that large of an import of data as it seems that code is a direct result of running out of disk space.

share|improve this answer

If i remember well error 28 should be for some problems writing on files. Were some file systems full at the time of the error? Maybe /tmp (or c:\temp) were full?

share|improve this answer
Linux baby, linux. ;) – Josh K May 28 '10 at 18:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.