Where is the default tmpdir of mysql?
Mysql data is stored in the data folder in the user-specified or default location. The default tmpdir is also stored in the data folder. MySQL temporary files are stored here and cannot be easily deleted.
Source of the error?
The upper directory /data where the MySQL data directory /data/mysql is located lacks disk space, causing MySQL to fail to start, so other useless directories in the /data directory except the mysql subdirectory are cleaned up. Restarting the discovery still failed. Check the error log.
See the following error:
/usr/local/mysql/bin/mysqld: Can't create/write to file '/data/tmp/ibbLmEoD' (Errcode: 13 - Permission denied)
It turns out that when cleaning up useless directories, the tmpdir-/data/tmp directory specified in the MySQL configuration file was accidentally deleted, causing some temporary files or tables when MySQL Server started to be unable to be written. , causing the startup to fail. After rebuilding the directory and granting the correct permissions, restart MySQL Server and start it normally.
Let’s talk about the MySQL temporary directory parameter:
Command line parameter format: --tmpdir=path
Configuration file parameter format:tmpdir=path
The temporary directory is used to store temporary files or temporary tables. The value can be a ":" (Unix) or ";" (Windows) separated list of paths that can be used in turn to spread the load to different disks. If the MySQL server is acting as a Slave, you cannot point this directory to a directory based on the memory file system or a directory that will be cleared when the host is restarted, because the Slave needs these files to copy the temporary table or perform the LOAD DATA INFILE operation. These files Loss will cause replication to fail. This means that the slave's tmpdir cannot be set to the default /tmp directory of the Linux system. For Slave, you can use another configuration item slave_load_tmpdir to set its temporary directory, so that Slave can not use the temporary directory set by the general option tmpdir. There is no such restriction for MySQL servers in non-Slave roles.
If the temporary directory does not exist or the permissions are incorrect, it will not only cause MySQL Server to fail to start, but also cause other MySQL utilities that may use the temporary directory to run abnormally. Many MySQL-related programs will read option values from the MySQL Server configuration file, such as the full backup program xtrabackup. The following error is caused by the temporary directory specified in the MySQL Server configuration file not existing.
xtrabackup_56: Can't create/write to file '/data/tmp/ibHbumcM' (Errcode: 2 - No such file or directory)
2014-07-23 16:04: 42 7f1b25c607e0 InnoDB: Error: unable to create temporary file; errno: 2
xtrabackup: innodb_init(): Error occured.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 389.
The above is the detailed content of Where is the default tmpdir of mysql?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.
