innodb_recover calls mysql with wrong pid file argument
Bug #253192 reported by
John Ferlito
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mylvmbackup (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mylvmbackup
If you set
innodb_recover=1 in the config file mylvmbackup tries to run mysql to perform the innodb recovery on th snapshot. The pid-file argument isn't being passed correctly and the recovery process fails.
A patch is attached.
root@db01:~# lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
root@db01:~# apt-cache policy mylvmbackup
mylvmbackup:
Installed: 0.6-4
Candidate: 0.6-4
Version table:
*** 0.6-4 0
500 http://
100 /var/lib/
Revision history for this message
| John Ferlito (johnf-inodes) wrote | #1 |
Revision history for this message
| S. Shvetsov (sshvetsov) wrote | #2 |
To post a comment you must log in.
Just started using mylvmbackup and encountered this exact error as soon as I enabled innodb_recover. Thanks for the patch John. Would be nice to have this bug fixed in Hardy. I guess it does not have catastrophic consequences, but can result in slower recovery from the generated backup.
According to app changelog [http://