From 2d5adc5823353cba2bd3e585bb75a4a298f4cbfd Mon Sep 17 00:00:00 2001 From: Peter Rajnoha Date: Thu, 28 Jun 2012 12:49:33 +0200 Subject: [PATCH] initscript: call vgchange -aay instead of -aly The clmvd init script called "vgchange -aly" before to activate all VGs in cluster environment. This activated all VGs, no matter if it was clustered or not. Auto activation for clustered VGs is not supported yet so the behaviour of -aay is still the same as before for clustered VGs. However, for non-clustered VGs, we need to check with the activation/auto_activation_volume_list whether the VG/LV should be activated on boot or not. --- WHATS_NEW | 1 + scripts/clvmd_init_red_hat.in | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/WHATS_NEW b/WHATS_NEW index 842a1889f..4a6df086a 100644 --- a/WHATS_NEW +++ b/WHATS_NEW @@ -1,5 +1,6 @@ Version 2.02.97 - =============================== + Use vgchange -aay instead of vgchange -ay in clmvd init script. Add activation/auto_activation_volume_list to lvm.conf. Add --activate ay to lvcreate. Add --activate ay to lvchange. diff --git a/scripts/clvmd_init_red_hat.in b/scripts/clvmd_init_red_hat.in index 3fc90c5cc..41700942a 100644 --- a/scripts/clvmd_init_red_hat.in +++ b/scripts/clvmd_init_red_hat.in @@ -87,7 +87,7 @@ start() ${lvm_vgscan} > /dev/null 2>&1 - action "Activating VG(s):" ${lvm_vgchange} -ayl $LVM_VGS || return $? + action "Activating VG(s):" ${lvm_vgchange} -aay $LVM_VGS || return $? touch $LOCK_FILE