mysql移动数据存放目录及问题
我计划更换数据库的存放目录，下面是我的操作步骤1：首先创建新的数据存放路径并授予权限[root@pacteralinuxmntsdc2formysql]#df-hFilesystemSizeUsedAvailUse%M
我计划更换数据库的存放目录，下面是我的操作步骤
1：首先创建新的数据存放路径并授予权限
[root@pacteralinux mntsdc2formysql]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 29G 20G 7.5G 73% / tmpfs 776M 0 776M 0% /dev/shm /dev/sdb1 69G 4.0G 62G 6% /mnt/resource /dev/sdc1 362G 53G 291G 16% /usr/local/Tomcat_Trans/webapps/infoSocketService/logs /dev/sdc2 131G 2.2G 122G 2% /mnt/mntsdc2formysql [root@pacteralinux mntsdc2formysql]# pwd /mnt/mntsdc2formysql [root@pacteralinux mntsdc2formysql]# mkdir mysqldata [root@pacteralinux mntsdc2formysql]# ll total 2050024 drwx------. 2 root root 16384 Dec 2 14:20 lost+found drwxr-xr-x. 2 root root 4096 Dec 26 13:29 mysqldata -rw-r--r--. 1 root root 2097152000 Dec 7 23:20 swapfile [root@pacteralinux mntsdc2formysql]# cd mysqldata/ [root@pacteralinux mysqldata]# chown mysql:mysql . [root@pacteralinux mysqldata]# cd .. [root@pacteralinux mntsdc2formysql]# ll total 2050024 drwx------. 2 root root 16384 Dec 2 14:20 lost+found drwxr-xr-x. 2 mysql mysql 4096 Dec 26 13:29 mysqldata -rw-r--r--. 1 root root 2097152000 Dec 7 23:20 swapfile [root@pacteralinux mntsdc2formysql]# chmod 755 mysqldata/ [root@pacteralinux mntsdc2formysql]# ll total 2050024 drwx------. 2 root root 16384 Dec 2 14:20 lost+found drwxr-xr-x. 2 mysql mysql 4096 Dec 26 13:29 mysqldata -rw-r--r--. 1 root root 2097152000 Dec 7 23:20 swapfile2：停止mysql
3：移动目录
我现在数据库的存放路径为
移动
[root@pacteralinux resource]# mv mysqldate/ /mnt/mntsdc2formysql/mysqldata/ [root@pacteralinux resource]# ll total 24 drwx------. 2 root root 16384 Nov 20 13:57 lost+found drwxr-xr-x. 2 root root 4096 Dec 2 15:02 mysqldataper drwxr-xr-x. 2 root root 4096 Dec 2 15:02 sdc3mnt [root@pacteralinux resource]# pwd /mnt/resource [root@pacteralinux resource]# cd /mnt/mntsdc2formysql/ [root@pacteralinux mntsdc2formysql]# ll total 2050024 drwx------. 2 root root 16384 Dec 2 14:20 lost+found drwxr-xr-x. 3 mysql mysql 4096 Dec 26 13:42 mysqldata -rw-r--r--. 1 root root 2097152000 Dec 7 23:20 swapfile [root@pacteralinux mntsdc2formysql]# cd mysqldata/ [root@pacteralinux mysqldata]# ll total 4 drwxr-xr-x. 7 mysql mysql 4096 Dec 26 13:32 mysqldate [root@pacteralinux mysqldata]# cd mysqldate/ [root@pacteralinux mysqldate]# ll total 176860 -rw-rw----. 1 mysql mysql 56 Nov 25 17:17 auto.cnf -rw-rw----. 1 mysql mysql 79691776 Dec 26 13:32 ibdata1 -rw-rw----. 1 mysql mysql 50331648 Dec 26 13:32 ib_logfile0 -rw-rw----. 1 mysql mysql 50331648 Nov 26 13:39 ib_logfile1 drwx------. 2 mysql mysql 4096 Nov 26 13:41 mysql drwx------. 2 mysql mysql 20480 Nov 26 17:00 mysqldb -rw-rw----. 1 mysql root 514836 Dec 26 13:32 pacteralinux.err drwx------. 2 mysql mysql 4096 Nov 26 13:41 performance_schema drwx------. 2 mysql mysql 4096 Nov 26 13:41 test drwx------. 2 mysql mysql 4096 Dec 9 16:49 weixindemo [root@pacteralinux mysqldate]# mv * ../ [root@pacteralinux mysqldate]# ll total 0 [root@pacteralinux mysqldate]# cd .. [root@pacteralinux mysqldata]# ll total 176864 -rw-rw----. 1 mysql mysql 56 Nov 25 17:17 auto.cnf -rw-rw----. 1 mysql mysql 79691776 Dec 26 13:32 ibdata1 -rw-rw----. 1 mysql mysql 50331648 Dec 26 13:32 ib_logfile0 -rw-rw----. 1 mysql mysql 50331648 Nov 26 13:39 ib_logfile1 drwx------. 2 mysql mysql 4096 Nov 26 13:41 mysql drwxr-xr-x. 2 mysql mysql 4096 Dec 26 13:48 mysqldate drwx------. 2 mysql mysql 20480 Nov 26 17:00 mysqldb -rw-rw----. 1 mysql root 514836 Dec 26 13:32 pacteralinux.err drwx------. 2 mysql mysql 4096 Nov 26 13:41 performance_schema drwx------. 2 mysql mysql 4096 Nov 26 13:41 test drwx------. 2 mysql mysql 4096 Dec 9 16:49 weixindemo [root@pacteralinux mysqldata]# rm -rf mysqldate/ [root@pacteralinux mysqldata]# ll total 176860 -rw-rw----. 1 mysql mysql 56 Nov 25 17:17 auto.cnf -rw-rw----. 1 mysql mysql 79691776 Dec 26 13:32 ibdata1 -rw-rw----. 1 mysql mysql 50331648 Dec 26 13:32 ib_logfile0 -rw-rw----. 1 mysql mysql 50331648 Nov 26 13:39 ib_logfile1 drwx------. 2 mysql mysql 4096 Nov 26 13:41 mysql drwx------. 2 mysql mysql 20480 Nov 26 17:00 mysqldb -rw-rw----. 1 mysql root 514836 Dec 26 13:32 pacteralinux.err drwx------. 2 mysql mysql 4096 Nov 26 13:41 performance_schema drwx------. 2 mysql mysql 4096 Nov 26 13:41 test drwx------. 2 mysql mysql 4096 Dec 9 16:49 weixindemo [root@pacteralinux mysqldata]#
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
1376
52
The relationship between mysql user and database
Apr 08, 2025 pm 07:15 PM
In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.
Do mysql need to pay
Apr 08, 2025 pm 05:36 PM
MySQL has a free community version and a paid enterprise version. The community version can be used and modified for free, but the support is limited and is suitable for applications with low stability requirements and strong technical capabilities. The Enterprise Edition provides comprehensive commercial support for applications that require a stable, reliable, high-performance database and willing to pay for support. Factors considered when choosing a version include application criticality, budgeting, and technical skills. There is no perfect option, only the most suitable option, and you need to choose carefully according to the specific situation.
RDS MySQL integration with Redshift zero ETL
Apr 08, 2025 pm 07:06 PM
Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.
How to fill in mysql username and password
Apr 08, 2025 pm 07:09 PM
To fill in the MySQL username and password: 1. Determine the username and password; 2. Connect to the database; 3. Use the username and password to execute queries and commands.
Query optimization in MySQL is essential for improving database performance, especially when dealing with large data sets
Apr 08, 2025 pm 07:12 PM
1. Use the correct index to speed up data retrieval by reducing the amount of data scanned select*frommployeeswherelast_name='smith'; if you look up a column of a table multiple times, create an index for that column. If you or your app needs data from multiple columns according to the criteria, create a composite index 2. Avoid select * only those required columns, if you select all unwanted columns, this will only consume more server memory and cause the server to slow down at high load or frequency times For example, your table contains columns such as created_at and updated_at and timestamps, and then avoid selecting * because they do not require inefficient query se
MySQL: The Ease of Data Management for Beginners
Apr 09, 2025 am 12:07 AM
MySQL is suitable for beginners because it is simple to install, powerful and easy to manage data. 1. Simple installation and configuration, suitable for a variety of operating systems. 2. Support basic operations such as creating databases and tables, inserting, querying, updating and deleting data. 3. Provide advanced functions such as JOIN operations and subqueries. 4. Performance can be improved through indexing, query optimization and table partitioning. 5. Support backup, recovery and security measures to ensure data security and consistency.
How to optimize MySQL performance for high-load applications?
Apr 08, 2025 pm 06:03 PM
MySQL database performance optimization guide In resource-intensive applications, MySQL database plays a crucial role and is responsible for managing massive transactions. However, as the scale of application expands, database performance bottlenecks often become a constraint. This article will explore a series of effective MySQL performance optimization strategies to ensure that your application remains efficient and responsive under high loads. We will combine actual cases to explain in-depth key technologies such as indexing, query optimization, database design and caching. 1. Database architecture design and optimized database architecture is the cornerstone of MySQL performance optimization. Here are some core principles: Selecting the right data type and selecting the smallest data type that meets the needs can not only save storage space, but also improve data processing speed.
How to view mysql
Apr 08, 2025 pm 07:21 PM
View the MySQL database with the following command: Connect to the server: mysql -u Username -p Password Run SHOW DATABASES; Command to get all existing databases Select database: USE database name; View table: SHOW TABLES; View table structure: DESCRIBE table name; View data: SELECT * FROM table name;
