holland-coredev team mailing list archive

[Chris Johnson <726776@xxxxxxxxxxxxxxxxxx>]

I think your right, this might be better solved by adding a small script
to the RHCS configuration that looks for the snapshot volume and removes
it if found then tries to start up.

However, this bring up another issue: lvm tagging. For this to work you
would have to have the ability to set a tag on the snapshot volume when
its created. Something like this:

# lvmcreate -L50GB --addtag @12345db1 -n mysql00_snapshop vgsan00

That will allow you to add an exception to the /etc/lvm/lvm.conf
volume_list so it can mount up that LV.

-- 
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.