diff options
| author | Peter Rajnoha <prajnoha@redhat.com> | 2012-06-28 12:49:33 +0200 |
|---|---|---|
| committer | Peter Rajnoha <prajnoha@redhat.com> | 2012-06-28 09:44:07 -0400 |
| commit | 2d5adc5823353cba2bd3e585bb75a4a298f4cbfd (patch) | |
| tree | e6c5821893d38833087e13406cee0a1a660f9d52 /scripts/clvmd_init_red_hat.in | |
| parent | f6a3ef4490ebcb2318fd98e79add2c910cf482c5 (diff) | |
| download | lvm2-2d5adc5823353cba2bd3e585bb75a4a298f4cbfd.tar.gz lvm2-2d5adc5823353cba2bd3e585bb75a4a298f4cbfd.tar.xz lvm2-2d5adc5823353cba2bd3e585bb75a4a298f4cbfd.zip | |
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.
Diffstat (limited to 'scripts/clvmd_init_red_hat.in')
| -rw-r--r-- | scripts/clvmd_init_red_hat.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/clvmd_init_red_hat.in b/scripts/clvmd_init_red_hat.in index 3fc90c5c..41700942 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 |