Information of 'diskinfo' command & mirror

[emulism]

I have two physical boot volumes in vg00.After I replaced the mirror with a new drive,I used 'diskinfo' & 'vgdisplay'command to check information. Why 'Total PE' &'Free PE'both disk 's not the same size? What's different of 'HP05' & 'HP07' rev level? what's different of ANSI version '2' & '3'? Any help wolud be greatly appreciated.

Regards,

P.S. This thread has been moved from Disk to HP-UX > VM and VxVM. -HP Forum Moderator

[Duncan Edmonstone]

Hi,

Why 'Total PE' &'Free PE'both disk 's not the same size?
- I don't know - it depends how you re-mirrored your drives? Are the two disks physically the same model?

What's different of 'HP05' & 'HP07' rev level?
- That's the firmware version on the disk. Ideally this should be the same on both disks (assuming both disks are the same model). If you have a support contract you might like to ask HP to upgrade it for you.

what's different of ANSI version '2' & '3'? Any help wolud be greatly appreciated.
- Not totally sure, but I would assume that this is the version of the ANSI SCSI standard that the drive supports.

HTH

Duncan

[Jon Mattatall]

Have you used different sized disks?
Post the results of
diskinfo /dev/rdsk/cxtydz
for the two drives and the "Physical Volumes" section of
vgdisplay -v /dev/vg00.

You may have a 4G and a 9G (or some other mismatch).

[emulism]

Thanks Mattatall for your answer.And the following is 'diskinfo' & 'vgdisplay'of both disk. Is mirror,Ok? Can u give technical reference about 'rev level' & 'ansi'that is my concern?

SCSI describe of /dev/rdsk/c2t6d0:
vendor: SEAGATE
product id: ST318436LC
type: direct access
size: 17783240 Kbytes
bytes per sector: 512
rev level: HP05
blocks per disk: 35566480
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2
(

SCSI describe of /dev/rdsk/c7t6d0:
vendor: SEAGATE
product id: ST318275LC
type: direct access
size: 17783240 Kbytes
bytes per sector: 512
rev level: HP07
blocks per disk: 35566480
ISO version: 0
ECMA version: 0
ANSI version: 2
removable media: no
response format: 2

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4350
VGDA 4
PE Size (Mbytes) 4
Total PE 8680
Alloc PE 4082
Free PE 4598
Total PVG 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 192
Current LE 48
Allocated PE 96
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 256
Used PV 2

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 2500
Current LE 625
Allocated PE 1250
Used PV 2

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 128
Allocated PE 256
Used PV 2

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 1600
Current LE 400
Allocated PE 800
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 800
Current LE 200
Allocated PE 400
Used PV 2

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 512
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c2t6d0
PV Status available
Total PE 4340
Free PE 2299
Autoswitch On

PV Name /dev/dsk/c7t6d0
PV Status available
Total PE 4340
Free PE 2299
Autoswitch On

Thanks for your future answer.

[Zigor Buruaga]

Hi,

Your Total PE and Free PE on your disks looks identical.
In my opinion, your mirror is OK.
About 'rev level' and 'ANSI version', see Duncan reply's.

Hope this helps.
Kind regards,
Zigor

[Eugeny Brychkov]

Disks are of different models. To check if they have latest firmware ask HP. But as soon as they have HO firmware (HPxx) they will work with hpux equipment.
Concerning replacing mirror disk: there're some actions to be done to repair mirror in additions to simple disk replacement - for boot disks there're some commands to reserve boot space and load boot code into it, restoring LVM config using vgcfgrestore, and finally syncing vg contents (data).
To check mirror consistency run
vgdisplay -v /dev/vg00
and you'll see if there're any stale PEs. If there're then mirror is not complete - try running 'vgsync vg00' command or reboot server and this command will be run automatically on bootup
Eugeny