holland-coredev team mailing list archive

[Andrew Garner <726776@xxxxxxxxxxxxxxxxxx>]

** Also affects: holland-backup/1.0
   Importance: Undecided
       Status: New

** Also affects: holland-backup/1.1
   Importance: Undecided
       Status: New

** Changed in: holland-backup/1.1
    Milestone: None => 1.1.0a2

** Changed in: holland-backup/1.1
       Status: New => In Progress

** Changed in: holland-backup/1.1
   Importance: Undecided => High

** Changed in: holland-backup/1.1
     Assignee: (unassigned) => Andrew Garner (muzazzi)

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

Title:
  holland-mysqllvm does not remove snapshot volume after crash

Status in Holland Backup Framework:
  In Progress
Status in holland-backup 1.0 series:
  New
Status in holland-backup 1.1 series:
  In Progress

Bug description:
  If a server crashes while a back up is running the snapshot volume is
  not removed. This is particularly problematic when lvm snapshots are
  being using in a cluster configured for HA-LVM and the active node is
  fenced. Because the passive node won't start with two LV's in the VG
  the cluster fails to start. A work around can be put in place by
  adding some lines to the init.d script that will remove any snapshot
  volumes found but it would be nice if holland could remove it.