May 25, 2012

Comment: How to change innodb_log_file_size safely

…11:51:16 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Restoring possible… ready for connections. Version: ’5.0.95′ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 Source distribution Also, I don’t …

Post: Troubleshooting MySQL Memory Usage

MySQL is troubleshooting memory usage. The problem usually starts like this – you have configured MySQL to use reasonable global buffers, such as innodb…File system 294352 (82672 + 211680) Lock system 318875832 (318747272 + 128560) Recovery system 0 (0 + 0) Threads 425080 (406936 + 18144) Dictionary …

Comment: How to recover a single InnoDB table from a Full Backup

…. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for…

Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

…? AFAIK, InnoDB is snapshot safe as long as database files and log files are on the same filesystem. But MySQL/InnoDB is not snapshot safe if DDL operations are in flight because DDL between MySQL (frm files) and InnoDB is not atomic and some failures are not recoverable (which can cause problems for recovery after…

Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

…, we bring up the new mysqld, which finds a crashed innodb, recovers this, and then it is being configured to become… the donor machine. Every once in a while the recovery of the innodb in the target location fails, though, even though it… have been experiencing this with many versions of MySQL. We are now using ‘service mysql stop’ instead of FLUSH TABLES WITH READ…

Comment: Connecting orphaned .ibd files

… course. Try this way: ./ibdconnect -o /var/lib/mysql/ibdata1 -f “/var/lib/mysql/mydb/st_results#P#p_1.ibd” -d… file a bug here https://bugs.launchpad.net/percona-data-recovery-tool-for-innodb

Comment: Percona Server vs MySQL on Intel 320 SSD

Patrick, There are two factors: 1. Speed of recovery is much better in MySQL/Percona Server 5.5 2. Having on SSD makes it also much faster. So having big log files is practical under these conditions. It still may be long, but that that painful as in old InnoDB.

Post: How to recover deleted rows from an InnoDB Tablespace

… objetive is Percona Data Recovery Tool for InnoDB. This is the tool that we use in our data recovery service and it’s…: 1- Extract all the InnoDB pages from the tablespace: First we need to download Percona Data Recovery Tool and compile all the… following link: http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:generating_a_table_definition With the table definition on…

Post: Magic Innodb Recovery self healing

… data on per table basics. Also if MySQL crashes during recovery lower values of innodb_force_recovery normally would not work. Reading Documentation one…”. So when dealing with Innodb recovery for bad corruptions you may want to: – Start with lower innodb_force_recovery settings and see which one…

Post: MySQL Crash Recovery

… is better solution. Innodb Recovery – Unless you have some hardware problems (99%) or found new Innodb bug (1%) Innodb recovery should be automatic … which you may experience related to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb tablespace recovery etc but I should write …