holland-coredev team mailing list archive

[Andrew Garner <1194988@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This is used by mysqldump-lvm to determine whether we should set any
innodb parameters.

This is documented in the MySQL docs here:

"* have_innodb

YES if mysqld supports InnoDB tables. DISABLED if --skip-innodb is used.

This variable was removed in MySQL 5.6.1. Use SHOW ENGINES instead."


This sort of breaks mysqldump-lvm with MySQL 5.6, since we'll fail to set a proper innodb-log-file-size.   5.6 will automatically regenerate new logs - but this might generate a lot of unnecessary io on the snapshot and eat up snapshot space.

Holland needs to check SHOW ENGINES instead.

** Affects: holland-backup
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/1194988

Title:
  have_innodb removed in mysql 5.6

Status in Holland Backup Framework:
  New

Bug description:
  This is used by mysqldump-lvm to determine whether we should set any
  innodb parameters.

  This is documented in the MySQL docs here:

  "* have_innodb

  YES if mysqld supports InnoDB tables. DISABLED if --skip-innodb is
  used.

  This variable was removed in MySQL 5.6.1. Use SHOW ENGINES instead."

  
  This sort of breaks mysqldump-lvm with MySQL 5.6, since we'll fail to set a proper innodb-log-file-size.   5.6 will automatically regenerate new logs - but this might generate a lot of unnecessary io on the snapshot and eat up snapshot space.

  Holland needs to check SHOW ENGINES instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/1194988/+subscriptions