vgreduce issue - current extents are unknown lvol

[Bernie Vande Griend]

We have some snapshot utilities that we used to bring over a disk from another HP-UX 11i server to a new one and imported it in. This was on a "time slice" so we had to mirror it over to a real disk. We've done that and are trying to get rid of the old disk with vgreduce. it fails because it has extents in use. However these extents are listed with ??? and no lvol:
08875 current ??? 00000 08876 current ??? 00001 08877 current ??? 00002
Never seen this before. Anyway to clear this so we can remove this disk? BTW- this same situation exists on the server we imaged the disk from.

[Siju Vadakkan]

Provide the following details :

1. strings /etc/lvmtab
2. more /etc/lvmpvg
3. vgdisplay -v vgname
4. lvdisplay -v lvname

[Bernie Vande Griend]

Included lvmtab, vgdisplay of vg02 and a pvdisplay of the disk with the issue. No PVG in place here. No lvol to list because its listed as ???

[psreedhar]

LVM prints ??? when the LV special file is deleted. Check you have the correct number of LV files. you can get the number of LVs from vgdisplay output.

[Michael Steele_2]

I believe this is a ghost disk.

1) vgchange -a y vg02 (* should say quorum not present *)

2) vgchange -a y -q y /dev/vg02 (* deactivate vg w/out quorum *)

3) vgreduce -f /dev/vg02 (* forced reduction of ghost disk *)

[Bernie Vande Griend]

I couldn't wait on this issue and as it was a new server, we just carved up another physical volume and vg and cpio'd the filesystems over and did a vgexport on the old. Michael- we did try the vgreduce -f but not with the quorum options, so I can't really say if that would have worked or not. Since I can't try anything further, I'll close this thread.

[Bernie Vande Griend]

We used another vg for this.