Bug #2444 .MYD and .MYI tables deleted (not truncated) on disk-full condition
Submitted: 19 Jan 2004 8:11 Modified: 22 Jan 2004 10:49
Reporter: Paul Eckert Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: ISAM storage engine Severity:S2 (Serious)
Version:3.23.53a OS:Linux (Red Hat 7.2)
Assigned to: CPU Architecture:Any

[19 Jan 2004 8:11] Paul Eckert
On a Linux Red Hat 7.2 system running MySQL 3.23, MySQL does not appear to handle disk-full conditions properly when neither a table update or the mysql log file can be written to due to a disk full condition.

In our case, the particular table that was being updated when the disk-full condition occurred had its .MYD file completely deleted, either before or during the failure of writes to the mysqld.log file which also lived on the disk that ran out of space.

The table's .MYD and .MYI file had to be completely restored from a backup as a result, altho the table's .frm file still existed.

How to repeat:
1. Put the tables and the log file on the same mount partition
2. Get close to disk capacity on that partition
3. Turn on full query debugging in my.cnf config file
4. Perform table updates until the disk is full.
5. Table files .MYD and .MYI disappear.
[22 Jan 2004 10:49] Alexander Keremidarski
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

After several different tests I was unable to repeat the problem with most recent versions of 3.23 and 4.0

In all cases mysqld waits for enough free diskspace.