Introduction
Yesterday Go2Linux was down, and all the problem was disk full, but how that happened?
Well, it was MySQL fault, the files like
mysql-bin.000001
mysql-bin.000002
mysql-bin.000003
mysql-bin.000004
mysql-bin.000005
....
mysql-bin.00000n
They were taking thousands of megas of disk space, let's see now why they are there, and how you can avoid running out of disk.
The binary log
The
I have a mysql table (MyISAM), called bla. The Version is 9 (mysql4)
Using a mysql5-server I did an alter table (add column, delete the same column). This is a simple trick to upgrade the table Version.
As shown by mysql:
$ echo "show table status from mydb like 'bla'\G" | mysql -p | grep Version
Enter password:
Version: 10
Normally the unix file command gives the same result, i.e.
I noticed that one of my servers was running out of disk space, due to heavy MySQL usage.
I stopped everything using the database, freed up some space and restarted mysqld.
Now, I checked my table with CHECK TABLE table and it gave me this:
+-------------------+-------+----------+---------------------------------------------------------------+
| Table | Op | Msg_type | Msg_text
I have a VM which has 2GB Ram, (full specs)
And I am setting up a site which has one table in particular with over a million records.
There's little or no usage of this particular database (perhaps once or twice a day) but simply running mysql grinds the whole server to a halt.
How do I create a local backup of a remote Amazon RDS MySQL database? What I need to know is how to make a complete full local backup of a MySQL database (not a remote Amazon snapshot) that can be used to restore to a new database anywhere, on any MySQL server (same version of course).
NOTE: I know how to import data from a flat file via MySQL.
I have 2 webservers running Apache 2.x on CentOS 5.x. One of them was started like 16 hours ago and has lots of free RAM (about 28GB out of 34GB).
My second server however, is running for a few weeks, and is constantly at 700 MB free RAM, no matter how much traffic there is. If I stop the Apache on it, it frees up another 400MB of RAM, so that isn't the problem.
Hi all. I know there are many tutorials on google on the subject, I'm not lazy to look, but because some procedures might be very old, and because I haven't done this before and have limited experience with mysql, I wanted to ask for an advice what is best to do.
Lets say I have machine A and machine B with mysql. On both machines I have the same database and table (only one table in the DB).
I have a question about getting a huge table to local machine from mysql running in AWS.
I just created a table which has a size of 2.3GB, however I have only 2 GB free disk space.
This lead into a situation that I even can not dump my table into a dump file which would cause error 28. Then I have two choices.
Clean up the disk with 300+MB free space.
I was using a PHP script running on background to grab data and insert them into the mysql database...
Email this page
