Missing size

[STANLY_1]

Hai all

We are facing a pblm with one D220(HP-UX 11.00) which is having 2 * 2 GB disks.
While comparing the LV sizes and the free size in VGs some space is missing
somewhere.when we do a vgscan it is checking for a disk which is not present.
I took over recently and not sure whether some disk was there or not.Following are the details.


lv1 stand /dev/dsk/c0t8d0 21
lv2 /dev/dsk/c0t8d0 64
lv3 / /dev/dsk/c0t8d0 35
lv4 /tmp /dev/dsk/c0t8d0 16 -- total pe 425
lv6 /opt /dev/dsk/c0t8d0 60
lv7 /usr /dev/dsk/c0t8d0 104
lv8 /var /dev/dsk/c0t8d0 125

lv10 3rdparty /dev/dsk/c0t5d0 50
lv11 mscomc /dev/dsk/c0t5d0 188
lv12 tmp/abcd /dev/dsk/c0t8d0 3 - total pe 246
lv14 tmp/tmpdir /dev/dsk/c0t5d0 5


- Physical volumes ---
PV Name /dev/dsk/c0t5d0
PV Status available
Total PE 508
Free PE 4

PV Name /dev/dsk/c0t8d0
PV Status available
Total PE 507
Free PE 2




#vgscan -a -v
Creating "/etc/lvmtab".
Couldn't stat physical volume "/dev/dsk/c1t2d0":
Invalid argument

/dev/vg00
/dev/dsk/c0t5d0
/dev/dsk/c0t8d0

Scan of Physical Volumes Complete

Thx
SJ

[Michael Tully]

it could be that there was a volume attached that is not currently.

Try this:

# ioscan -fnC disk

This will identify exactly what the system sees in the way of disks.
If your unsure, post the ioscan output.

[STANLY_1]

Hi# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST32550W
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST32550W
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401TA
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0


Regds
SJ

[Michael Tully]

Hi,

Everything is fine. The reason 'vgscan' complained, is that it tried to do something with your CD ROM drive. The device is
disk 2 8/16/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401TA
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0

Don't worry

Cheers
Michael

[Michael Tully]

If your still worried about the size difference of the volume groups, post the output of this:

# vgdisplay -v

From what I can see, there is no obvious problem other than the physical extent size of the disks are slightly different.