summaryrefslogtreecommitdiffstats
path: root/tools/toollib.c
diff options
context:
space:
mode:
authorDave Wysochanski <dwysocha@redhat.com>2010-06-28 20:36:18 +0000
committerDave Wysochanski <dwysocha@redhat.com>2010-06-28 20:36:18 +0000
commitbc963e745cdaafad76223fd99ebc8af6bf52cfa4 (patch)
tree52ec053bb56e2a58fe419d7be0c379eafde822f7 /tools/toollib.c
parentc6894cf03188c2de8e340010168060db35df1ed1 (diff)
downloadlvm2-bc963e745cdaafad76223fd99ebc8af6bf52cfa4.tar.gz
lvm2-bc963e745cdaafad76223fd99ebc8af6bf52cfa4.tar.xz
lvm2-bc963e745cdaafad76223fd99ebc8af6bf52cfa4.zip
Define vgmetadatacopies in vgchange man page.
This patch adds a vgmetadatacopies parameter for metadata balancing. This parameter provides a simple way for users to create a policy for placing metadata on PVs automatically by LVM. The behavior is implemented inside LVM by managing the 'ignore' mda bits. We chose the name 'vgmetadatacopies' as this is a natural extension to the existing parameter 'pvmetadatacopies' / 'metadatacopies' in pvcreate. This is a first step at VG parameter based metadata balancing. Most users will probably want to state that they want a certain number of PVs to contain metadata, and they may be less concerned about a specific number of metadata copies in the volume group. However, for default values (pvmetadatacopies is 1 by default), the number of metadatacopies in the volume group, and the number of PVs with metadata are the same. In the future we could add vgmetadatacopiespvs to define more specifically the number of pvs in the VG that contain metadata, but for now we start with this parameter. Another possible future extension would be to define a specific pv tag to mark the set of PVs that should be used for metadata balancing. This tag based approach could be used in conjunction with 'vgmetadatacopies'. Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
Diffstat (limited to 'tools/toollib.c')
0 files changed, 0 insertions, 0 deletions