pvdisplay -v shows ???

[Irfan Ahmed_1]

Hi all,
I have on disk c0t14d0 of vg01 some unreferenced logical volumes that I cannot get rid of. I recognised them, because the first 10 PEs of that disk were not used and pvdisplay -v showed ??? for the lvol they belong to.

I want to know how can I get rid of it?

Thanks
-Irfan

[somemore]

Hi,

check for the LV created on the PV,
make sure which are the LV you have data, if the unreferenced LV is on the disk, and
if it has the filesystem create the mount
point and mount the LV, make sure you are not going to loose the data, before deleting
the unreferenced LV.

Steps.

Mount the LV
if it is not required u can remove the lv

[Sunil Sharma_1]

Irfan,

It looks like somebody deleted device file of some logical volume that's why the physical extent belong to that logical volume are showing as ???? .

you can recreate device file of that logical volume using mknod and then remove lvol with lvremove command.

Sunil

[Suraj_2]

Hi

As indicated by Sunil, seems some LV device files are missing.See the ITRC document KBRC00002238.

Here is the sollution as provided by that doc


pvdisplay -v shows ??? DocId: KBRC00002238 Updated: 8/22/01 2:09:00 PM

PROBLEM
pvdisplay -v has ??? in the Logical Volume column.

# pvdisplay -v /dev/dsk/c#t#d# of the disk shows the following:
---Physical Extents---
PE Status LV LE
0000 current /dev/vg05/lvol12 0000
0001 current /dev/vg05/lvol12 0001
0002 current /dev/vg05/lvol12 0002
...
3061 current ??? 0000
...
3210 current ??? 0149



RESOLUTION
The reason this is happening is the device file for the logical volume was
removed. The following steps will show how to find the missing logical volume,
recreate and remove it properly.


1. ll /dev/vg05
example output:

crw-r----- 1 root sys 64 0x00000a Nov 3 1999 rlvol10
crw-r----- 1 root sys 64 0x00000d Dec 27 14:16 rlvol13
crw-r----- 1 root sys 64 0x00000e Dec 27 14:16 rlvol14

Make a note of all the minor numbers that are shown. 0x00000a, 0x00000d, etc..
would be the minor number in this case for /dev/vg05

The minor number will be used later for testing missing numbers. Notice the
minor numbers increment like 0x000001, 0x000002, 0x000003, etc...
Look for numbers that may have been skipped. Remember these numbers are HEX so
they increment like 0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f,g,h,10,11,12..1a..1h

If 0x000008 was skipped then the following will need to be done where the 8
would be used instead of the #.

NOTE: Do not try minor numbers if they show up in the previous ll
output. Only use ones that do not show up.

2. mknod /dev/vg05/test# b 64 0x00000#

Note: the # in test# is used to correspond to the # in the minor number.
This will help clean up later and make it easier to reference later in this
document.

3. pvdisplay -v /dev/dsk/c1t11d0

The ??? will go away when the correct missing minor number is used.

If ??? still shows up in the pvdisplay then try the next minor number. This
needs to be repeated until the right minor number is found. When the right
minor number is chosen the ??? will go away and a lvol name will appear in
their place. Make a note of this lvol name.

4. Once the lvol name has been found. Do the following

mknod /dev/vg05/test# c 64 0x00000#
lvremove /dev/vg05/test#

5. Clean up all the test# that were created in step 2 but not used in step 4.

rm /dev/vg05/test4

Hope this helps

Rgds
Suraj

[Irfan Ahmed_1]

Later we found that each PE 0-9 on disk c0t14d0 belongs to a logical volume of
size 1, by creating device files using
"mknod /dev/vg01/testi b 64 0x01000i"
"mknod /dev/vg01/rtesti c 64 0x01000i"
and checking for each "i" if pvdisplay -v displays a name insted of "???".

When we found all minor numbers "0x01000i", we tried to delete them using
lvremove. But we failed because the logical volumes were not part of vg01.

bye
-Irfan

[Nguyen Anh Tien]

I think you pv is fragment.
Let try
fsadm â F vxfs â D /[mount_point]
fsadm â F vxfs â d /[mount_point]
Mount_point is mount point of you lvol