Oracle 5.0 Reference Manual page 2984

• Do not rule out your server hardware when diagnosing problems. Defective hardware can be the
cause of data corruption. Particular attention should be paid to your memory and disk subsystems
when troubleshooting hardware.
C.5.4.3. How MySQL Handles a Full Disk
This section describes how MySQL responds to disk-full errors (such as "no space left on device"), and
to quota-exceeded errors (such as "write failed" or "user block limit reached").
This section is relevant for writes to
binary log index file, except that references to "row" and "record" should be understood to mean
"event."
When a disk-full condition occurs, MySQL does the following:
• It checks once every minute to see whether there is enough space to write the current row. If there is
enough space, it continues as if nothing had happened.
• Every 10 minutes it writes an entry to the log file, warning about the disk-full condition.
To alleviate the problem, you can take the following actions:
• To continue, you only have to free enough disk space to insert all records.
• To abort the thread, you must use
the disk (in one minute).
• Other threads might be waiting for the table that caused the disk-full condition. If you have several
"locked" threads, killing the one thread that is waiting on the disk-full condition enables the other
threads to continue.
Exceptions to the preceding behavior are when you use
or when the indexes are created in a batch after
statement. All of these statements may create large temporary files that, if left to themselves, would
cause big problems for the rest of the system. If the disk becomes full while MySQL is doing any of
these operations, it removes the big temporary files and mark the table as crashed. The exception is
that for
ALTER
C.5.4.4. Where MySQL Stores Temporary Files
On Unix, MySQL uses the value of the
in which to store temporary files. If
/tmp, /var/tmp, or /usr/tmp.
On Windows, Netware and OS2, MySQL checks in order the values of the TMPDIR, TEMP, and
environment variables. For the first one found to be set, MySQL uses it and does not check those
remaining. If none of TMPDIR, TEMP, or
is usually C:\windows\temp\.
If the file system containing your temporary file directory is too small, you can use the
option to
mysqld
In MySQL 5.0, the
robin fashion. Paths should be separated by colon characters (":") on Unix and semicolon characters
(";") on Windows, NetWare, and OS/2.
Administration-Related Issues
MyISAM
mysqladmin
TABLE, the old table is left unchanged.
TMPDIR
to specify a directory in a file system where you have enough space.
[424] option can be set to a list of several paths that are used in round-
--tmpdir
Note
To spread the load effectively, these paths should be located on different
physical disks, not different partitions of the same disk.
tables. It also applies for writes to binary log files and
kill. The thread is aborted the next time it checks
REPAIR TABLE
LOAD DATA INFILE
environment variable as the path name of the directory
TMPDIR
is not set, MySQL uses the system default, which is usually
are set, MySQL uses the Windows system default, which
TMP
2964
or
OPTIMIZE TABLE
or after an
ALTER TABLE
--tmpdir
TMP
[424]