[Bug 375371] [NEW] MySQL must not use /tmp

Launchpad Bug Tracker 375371 at bugs.launchpad.net
Tue May 12 14:23:25 BST 2009


You have been subscribed to a public bug:

I noticed that the my.cnd points the tmpdir to /tmp, which IMHO might be
fatal.

>From the MySQL site:
If the MySQL server is acting as a replication slave, you should not set --tmpdir to point to a directory on a memory-based file system or to a directory that is cleared when the server host restarts. A replication slave needs some of its temporary files to survive a machine restart so that it can replicate temporary tables or LOAD DATA INFILE operations. If files in the temporary file directory are lost when the server restarts, replication fails. 
http://dev.mysql.com/doc/refman/5.0/en/temporary-files.html

>From the FHS:
/tmp/ 	Temporary files (see also /var/tmp). Often not preserved between system reboots.
http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

It might even be, that Ubuntu clears /tmp.

Anyhow, /tmp can be considered lost upon system restart - any file that
should survive a system restart belong to /var/tmp

/var/tmp/       Temporary files to be preserved between reboots.

so please consider 
tmpdir=/var/tmp

I dunno if apparmor needs to be adjusted, but I guess I will soon find
out...

regards
Philipp

** Affects: mysql-dfsg-5.0 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
MySQL must not use /tmp
https://bugs.launchpad.net/bugs/375371
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.



More information about the Ubuntu-server-bugs mailing list