mylvmbackup-discuss team mailing list archive

["Wong, Patrick" <pwong@xxxxxxxxx>]

Nevermind, I found out the problem.

 

I modified sub do_innodb_recover () in the script to specify
-innodb_data_home_dir and  -innodb_log_group_home_dir when calling
mysqld_safe

 

In the error log it now shows:

 

090202 13:46:33 mysqld_safe Starting mysqld daemon with databases from
/var/tmp/mylvmbackup/mnt/backup/var

090202 13:46:34  InnoDB: Started; log sequence number 0 48400

090202 13:46:34  InnoDB: Starting shutdown...

090202 13:46:35  InnoDB: Shutdown completed; log sequence number 0 48400

090202 13:46:35 mysqld_safe mysqld from pid file
/var/tmp/mylvmbackup_recoverserver.pid ended

 

I'm not sure if that is normal. Anyone know?

 

________________________________

From: mylvmbackup-discuss-bounces+pwong=ebmud.com@xxxxxxxxxxxxxxxxxxx
[mailto:mylvmbackup-discuss-bounces+pwong=ebmud.com@xxxxxxxxxxxxxxxxxxx]
On Behalf Of Wong, Patrick
Sent: Monday, February 02, 2009 1:10 PM
To: mylvmbackup-discuss@xxxxxxxxxxxxxxxxxxx
Subject: [Mylvmbackup-discuss] innodb-recover option not working for me

 

Hi All,

  It seems I'm running into problems with the innodb-recover=1 option in
mylvmbackup.conf.  

 

After running mylvmbackup, I notice that it writes to the error log.  In
the error log is the following:

 

090202 12:56:53 mysqld_safe Starting mysqld daemon with databases from
/var/tmp/mylvmbackup/mnt/backup

InnoDB: Unable to lock /var/mysql_data/var/ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

090202 12:56:53  InnoDB: Retrying to lock the first data file

InnoDB: Unable to lock /var/mysql_data/var/ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

InnoDB: Unable to lock /var/mysql_data/var/ibdata1, error: 11

InnoDB: Check that you do not already have another mysqld process

InnoDB: using the same InnoDB data or log files.

.....

InnoDB: Error number 11 means 'Resource temporarily unavailable'.

InnoDB: Some operating system error numbers are described at

InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html

InnoDB: Could not open or create data files.

InnoDB: If you tried to add new data files, and it failed here,

InnoDB: you should now edit innodb_data_file_path in my.cnf back

InnoDB: to what it was, and remove the new ibdata files InnoDB created

InnoDB: in this failed attempt. InnoDB only wrote those files full of

InnoDB: zeros, but did not yet use them in any way. But be careful: do
not

InnoDB: remove old data files which contain your precious data!

090202 12:58:33 [ERROR] Plugin 'InnoDB' init function returned error.

090202 12:58:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
failed.

090202 12:58:33 mysqld_safe mysqld from pid file
/var/tmp/mylvmbackup_recoverserver.pid ended

 

 

It seems the 2nd mysql instance started by mylvmbackup is syncing to the
wrong innodb datafile.  Does anyone know what could be wrong? Maybe
something in my conf file?

 

Thanks