pvmove cluster fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | Remove unused and wrongly set cluster VG flag from clvmd lock query command.WHATS_NEW lib/ | +2 | 0 replies | |
| 2/4 | Use new flag PVMOVE_EXCLUSIVE in update_metatada call.tools/ | +11 | 0 replies | |
| 3/4 | Do not allow pvmove if some affected LVs are activated locally or on more nodes while others are activated exclusively.WHATS_NEW tools/ | +25 | 0 replies | |
| 3/4 | Do not allow pvmove if some affected LVs are activated locally or on more nodes while others are activated exclusively. | +0 | 0 replies | |
| 4/4 | Keep exclusive activation in pvmove if LV is already active.WHATS_NEW lib/ tools/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] pvmove cluster fixes
Various locking changes in previous releases, mainly commit
commit bd86888d7406cdb8ba20ff3d3b807fabcc7ba0db
Pass exclusive LV locks to all nodes in the cluster.
This was the intended behaviour, as described in the lvchange man page, so you have complete control through volume_list in lvm.conf, but the code seems to have been treating -ae as local-only for a very long time.
caused pvmove to stopped working if an LV is activated exclusively.
Milan
Milan Broz (4):
Remove unused and wrongly set cluster VG flag from clvmd lock query
command.
Use new flag PVMOVE_EXCLUSIVE in update_metatada call.
Do not allow pvmove if some affected LVs are activated locally or
on more nodes while others are activated exclusively.
Keep exclusive activation in pvmove if LV is already active.
WHATS_NEW | 3 ++ lib/locking/cluster_locking.c | 2 +- lib/locking/locking.c | 2 +- tools/pvmove.c | 44 +++++++++++++++++++++++++++++++++------- 4 files changed, 41 insertions(+), 10 deletions(-)
Signature · 1 line
1.7.9.1