holland-coredev team mailing list archive

[Andrew Garner <1194979@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a snapshot is invalidated and mysqld crashes as a result, there is
no information logged about what went wrong.  Only by correlating dmesg
or other logging to the time when holland failed is it all clear that
the reason a backup failed was due to snapshot invalidation (e.g. ran
out of space allocated to the snapshot)

holland lvm plugins really should always check the snapshot volume at
the end and if lv_attr has an 'S' flag, we should verbosely log that the
snapshot appears to have been invalidated.

Further the mysqldump-lvm plugin should try to grab the last few lines
of the mysqld error log to indicate what failed, if holland's spawned
mysqld process is not running when we attempt to terminate it.

** 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/1194979

Title:
  mysqldump-lvm does not log enough on failure

Status in Holland Backup Framework:
  New

Bug description:
  When a snapshot is invalidated and mysqld crashes as a result, there
  is no information logged about what went wrong.  Only by correlating
  dmesg or other logging to the time when holland failed is it all clear
  that the reason a backup failed was due to snapshot invalidation (e.g.
  ran out of space allocated to the snapshot)

  holland lvm plugins really should always check the snapshot volume at
  the end and if lv_attr has an 'S' flag, we should verbosely log that
  the snapshot appears to have been invalidated.

  Further the mysqldump-lvm plugin should try to grab the last few lines
  of the mysqld error log to indicate what failed, if holland's spawned
  mysqld process is not running when we attempt to terminate it.

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