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.
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:// www.lenzg. net/mylvmbackup /ChangeLog] this bug was fixed by author between versions 0.7 and 0.8 on 2008-03-03.