diff options
| author | Milan Broz <mbroz@redhat.com> | 2012-03-26 20:32:58 +0000 |
|---|---|---|
| committer | Milan Broz <mbroz@redhat.com> | 2012-03-26 20:32:58 +0000 |
| commit | dcd90bc501677849ee50b430ea956be7392dffae (patch) | |
| tree | 18ede1641cec6b19a0191e6f47fa0e5d279c4dcb /WHATS_NEW | |
| parent | 3366541aabbc6c74975ef3660d96139a835c6ba8 (diff) | |
| download | lvm2-dcd90bc501677849ee50b430ea956be7392dffae.tar.gz lvm2-dcd90bc501677849ee50b430ea956be7392dffae.tar.xz lvm2-dcd90bc501677849ee50b430ea956be7392dffae.zip | |
Do not allow pvmove if some affected LVs are activated
locally or on more nodes while others are activated exclusively.
Current pvmove code can either use local mirror (for exclusive
activation) or cmirror (for clustered LVs).
Because the whole intenal pvmove LV is just segmented LV containing
segments of several top-level LVs, code cannot properly handle
situation if some segment need to be activated exclusively.
Previously, it wrongly activated exclusive LV on all nodes
(locing code allowed it) but now this is no lnger possible.
If there is exclusively activated LV, pvmove is only
possible if all affected LVs are aslo activated exclusively.
(Note that in non-exclusive mode pvmove still activates LVs
on other nodes during move.)
# lvchange -aly vg_test/lv1
# lvchange -aey vg_test/lv2
# pvmove -i 1 /dev/sdc
Error locking on node bar-01: Device or resource busy
Error locking on node bar-03: Volume is busy on another node
...
Failed to activate lv2
Diffstat (limited to 'WHATS_NEW')
| -rw-r--r-- | WHATS_NEW | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1,5 +1,6 @@ Version 2.02.96 - ================================ + Disallow pvmove for exclusive LV if some affected LVs are not exclusively activated. Remove unused and wrongly set cluster VG flag from clvmd lock query command. Fix pvmove for exclusively activated LV pvmove in clustered VG. (2.02.86) Always free hash table on update_pvid_to_vgid() in lvmetad. |