Add infrastructure for metadata balancing.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest21 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/21 | Change 'filler' to 'flags' in on-disk 'raw_locn' structure.lib/ | +1 | 0 replies | |
| 2/21 | Add text format specific 'rlocn' disable flag and access functions.include/ lib/ lib/ +1 more | +25 | 0 replies | |
| 3/21 | Add format independent flag and functions to disable mdas.lib/ lib/ lib/ | +20 | 0 replies | |
| 4/21 | Move dev_open / dev_close outside _vg_read_raw_area().lib/ | +30 | 0 replies | |
| 5/21 | Move dev_open/dev_close outside vgname_from_mda().lib/ lib/ | +13 | 0 replies | |
| 6/21 | Allow raw_read_mda_header to be called from text_label.c.lib/ lib/ lib/ +1 more | +37 | 0 replies | |
| 7/21 | Ensure in-memory state matches on-disk state of mda disable bit.lib/ lib/ | +5 | 0 replies | |
| 8/21 | Add vg field to struct physical_volume and find_vg_by_pv().lib/ lib/ lib/ | +8 | 0 replies | |
| 9/21 | Add mda_locn_match() internal library function.lib/ lib/ lib/ | +52 | 0 replies | |
| 10/21 | Define new functions and vgs/pvs fields related to mda disable/enable.lib/ lib/ lib/ +1 more | +120 | 0 replies | |
| 11/21 | Add --metadatadisable to pvchange, allowing for disabling of metadata areas.tools/ tools/ tools/ | +32 | 0 replies | |
| 12/21 | Update pvchange, pvs and vgs man pages for metadata disable.man/ man/ man/ | +8 | 0 replies | |
| 13/21 | Add tests for metadata balance - set/clear/display per-PV disable bit.test/ | +41 | 0 replies | |
| 14/21 | Add metadata balance arguments, update vgcreate man page and help.man/ tools/ tools/ | +33 | 0 replies | |
| 15/21 | Add vg metadata balance parameters with defaults.lib/ lib/ lib/ +1 more | +21 | 0 replies | |
| 16/21 | Add vg get/set methods for metadata balance min/max.lib/ lib/ | +59 | 0 replies | |
| 17/21 | Make metadata_balance_{min|max} persistent on disk.lib/ lib/ | +16 | 0 replies | |
| 18/21 | Add vg_mda_balance_{min|max} display fields to 'vgs' command.lib/ lib/ | +26 | 0 replies | |
| 19/21 | Add vg metadata balance parameters to vgchange man page and help.man/ tools/ | +27 | 0 replies | |
| 20/21 | Update vgchange tool to handle metadata balance min/max.tools/ | +76 | 0 replies | |
| 21/21 | Update metadatabalance tests to include sanity checks for vgchange.test/ | +25 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/21] Add infrastructure for metadata balancing.
This patchset is a third round of the metadata balancing support, and builds on the second round of patches already submitted. It adds the infrastructure to set a bit inside the mda header on a per-PV basis, control it from pvchange, display the number of mdas with this bit set on a particular PV or VG, and adds VG 'min' / 'max' parameters to control the per-PV bits.
Changes from the second round include:
1) Define the vg-level parameters which control metadata balancing:
a) vg_mda_balance_max: a number indicating the maximum number of PVs to contain enabled metadata areas; range is vg_mda_balance_min:# of PVs in VG
b) vg_mda_balance_min: a number indicating the minimum number of PVs to contain enabled metadata areas; range 1:vg_mda_balance_max
2) Add metadata_balance_{min|max} to struct volume_group, and store these parameters on disk in vg metadata.
3) Update vgchange to take metadatabalance{min|max} parameters.
4) Various small bugs fixed in the second round of patches.
Still TODO:
1) Implement the disable of mdas properly by disabling certain metadata_area_ops functions. I began this work, then ran into some lvmcache issues that need to be resolved. Code is isolated to one patch (not included in this set).
2) Implement the setting of the disable bit on various PVs when the metadatabalance{min|max} parameters are given to vgchange. Should be fairly straightforward - setting a lower 'max' value might cause metadata disable bits set on PVs, and setting a higher 'min' value may cause metadata disable bits cleared on PVs.
3) Consider renaming the 'disable' to 'enable' as this is more consistent with the 'min' and 'max' parameters