This problem seems to affect only systems with HACMP but it's not rounded to those system.
If I create 2 lv whithe the following names "goofie" and "goofie.new" also in different Vs, the importvg command, ran with the -L option (as it's done by C-SPOC) will fail.
This is because of an error in the importvg command, while "learning" from the VGDA contained in one of the pvs of the importing VG.
The failing command row is:
lqueryvg -p $KEY_DEVICE -L | (awk '{print $2" "$1}'|cut -d'.' -f1) > /tmp/lvverify$$
With the "cut -d'.' -f1" command, the string ".new" of the name of LV goofie.new ... will be lost with the result of importvg command will incorrectly believe that's whe are trying to import a VG with an LV name identical to an already existing one
If I create 2 lv whithe the following names "goofie" and "goofie.new" also in different Vs, the importvg command, ran with the -L option (as it's done by C-SPOC) will fail.
This is because of an error in the importvg command, while "learning" from the VGDA contained in one of the pvs of the importing VG.
The failing command row is:
lqueryvg -p $KEY_DEVICE -L | (awk '{print $2" "$1}'|cut -d'.' -f1) > /tmp/lvverify$$
With the "cut -d'.' -f1" command, the string ".new" of the name of LV goofie.new ... will be lost with the result of importvg command will incorrectly believe that's whe are trying to import a VG with an LV name identical to an already existing one