Dave Wysochanski a9d8bf269a Allow 'all' and 'unmanaged' values for --vgmetadatacopies. ... Allowing an 'all' and 'unmanaged' value is more intuitive, and provides a simple way for users to get back to original LVM behavior of metadata written to all PVs in the volume group. If the user requests "--vgmetadatacopies unmanaged", this instructs LVM not to manage the ignore bits to achieve a specific number of metadata copies in the volume group. The user is free to use "pvchange --metadataignore" to control the mdas on a per-PV basis. If the user requests "--vgmetadatacopies all", this instructs LVM to do 2 things: 1) clear all ignore bits, and 2) set the "unmanaged" policy going forward. Internally, we use the special MAX_UINT32 value to indicate 'all'. This 'just' works since it's the largest value possible for the field and so all 'ignore' bits on all mdas in the VG will get cleared inside _vg_metadata_balance(). However, after we've called the _vg_metadata_balance function, we check for the special 'all' value, and if set, we write the "unmanaged" value into the metadata. As such, the 'all' value is never written to disk. Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>		2010-06-28 20:40:01 +00:00
..
columns.h	Add vg_mda_copies display field to 'vgs' command.	2010-06-28 20:37:23 +00:00
report.c	Allow 'all' and 'unmanaged' values for --vgmetadatacopies.	2010-06-28 20:40:01 +00:00
report.h	Separate PV label attributes which do not need parse metadata when reporting.	2009-02-09 09:45:49 +00:00