David Teigland 18f451e09e handle duplicate vgids ... The approach to duplicate VGIDs has been that it is not possible or not allowed, so the behavior has been undefined. The actual result was unpredictable and/or broken, and generally unhelpful. Improve this by recognizing the problem, displaying the VGs, and printing a warning to fix the problem. Beyond this, using VGs with duplicate VGIDs remains undefined, but should work well enough to correct the problem with vgchange -u. It's possible to create this condition without too much difficulty by cloning PVs, followed by an incomplete attempt at making the two VGs unique (vgrename and pvchange -u, but missing vgchange -u.)		2022-01-13 10:01:24 -06:00
..
api	shellcheck: updates	2021-04-23 23:00:55 +02:00
dbus	tests: test_pv_symlinks works only with /dev dir	2021-03-28 00:21:38 +01:00
lib	cov: ignoring	2021-09-27 18:56:14 +02:00
shell	handle duplicate vgids	2022-01-13 10:01:24 -06:00
unit	cov: ignore close result	2021-10-15 23:40:29 +02:00
.gitignore	test: add results/ to .gitignore	2016-12-10 18:00:25 +00:00
Makefile.in	vdo: Rename vdoimport to lvm_import_vdo.	2021-08-26 17:13:59 +02:00