Oracle 5.0 Reference Manual page 1247

Caution
InnoDB
that has commit, rollback, and crash-recovery capabilities to protect user data.
However, it cannot do so if the underlying operating system or hardware
does not work as advertised. Many operating systems or disk subsystems may
delay or reorder write operations to improve performance. On some operating
systems, the very
data for a file has been flushed might actually return before the data has been
flushed to stable storage. Because of this, an operating system crash or a
power outage may destroy recently committed data, or in the worst case, even
corrupt the database because of write operations having been reordered. If
data integrity is important to you, you should perform some "pull-the-plug" tests
before using anything in production. On Mac OS X 10.3 and up,
a special
write-back cache.
On ATA/SATA disk drives, a command such
work to disable the write-back cache. Beware that some drives or disk
controllers may be unable to disable the write-back cache.
Two important disk-based resources managed by the
data files and its log files. If you specify no
auto-extending data file, slightly larger than 10MB, named
and
ib_logfile0 ib_logfile1
the
innodb_log_file_size
parameters as discussed in the following examples. Naturally, edit the settings to suit your
InnoDB
hardware and requirements.
Caution
It is not a good idea to configure
volumes. Otherwise, the files might be locked by other processes and become
unavailable for use by MySQL.
The examples shown here are representative. See
System Variables" for additional information about InnoDB-related configuration parameters.
To set up the tablespace files, use the
InnoDB
section of the
[mysqld]
innodb_data_file_path
more than one data file, separate them by semicolon (";") characters:
innodb_data_file_path=datafile_spec1[;datafile_spec2]...
For example, the following setting explicitly creates a tablespace having the same characteristics as
the default:
[mysqld]
innodb_data_file_path=ibdata1:10M:autoextend
This setting configures a single 10MB data file named
the file is given, so by default,
Sizes are specified using K, M, or
A tablespace containing a fixed-size 50MB data file named
named in the data directory can be configured like this:
ibdata2
[mysqld]
innodb_data_file_path=ibdata1:50M;ibdata2:50M:autoextend
Configuration
InnoDB
is a transaction-safe (ACID compliant) storage engine for MySQL
system call that should wait until all unwritten
fsync()
file flush method. Under Linux, it is advisable to disable the
fcntl()
InnoDB
in the MySQL data directory. Their size is given by the size of
[1247] system variable. To get good performance, explicitly provide
innodb_data_file_path
option file. On Windows, you can use
my.cnf
[1240] should be a list of one or more data file specifications. If you name
creates it in the MySQL data directory.
InnoDB
suffix letters to indicate units of KB, MB, or GB.
G
1227
hdparm -W0 /dev/hda
storage engine are its tablespace
InnoDB
configuration options, MySQL creates an
and two log files named
ibdata1
to use data files or log files on NFS
InnoDB
Section 14.2.2, "InnoDB
my.ini
that is auto-extending. No location for
ibdata1
and a 50MB auto-extending file
ibdata1
uses
InnoDB
may
Startup Options and
[1240] option in the
instead. The value of