I agree we should remove snapshots more aggressively. There has been a lot of talk of removing old snapshots if holland sees one exists rather than just failing due to a naming conflict (as we are currently). I wrote the code to do this last week and we should see it for 1.0.8 in the coming weeks.
I am not sure we can address this particular use case however, since holland can only remove snapshots when it actually runs or is running and has a chance to do so. If I am understanding correctly, in the case a of a crash it's unlikely holland would ever even have the chance to run before the snapshot becomes a problem. What would you like holland to do in that case? -- You received this bug notification because you are a member of Holland Discuss, 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: Confirmed 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. _______________________________________________ Mailing list: https://launchpad.net/~holland-coredev Post to : [email protected] Unsubscribe : https://launchpad.net/~holland-coredev More help : https://help.launchpad.net/ListHelp
