LVM and VxVM
cancel
Showing results for 
Search instead for 
Did you mean: 

Mirroring a root disk on a VPAR

 
SOLVED
Go to solution
EU-Admins-UNIX
Regular Advisor

Mirroring a root disk on a VPAR

Hi

 

I am just mirroring a test vpars root disk.  Whem extending lvols 1, 2 & 3, I get:

 

root@hathor at /probkup =>lvextend -m 1 /dev/vg00/lvol1 /dev/disk/disk141
The newly allocated mirrors are now being synchronized. This operation will
take some time. Please wait ....
Logical volume "/dev/vg00/lvol1" has been successfully extended.
lvlnboot: LIF information corrupt or not present on  "/dev/disk/disk141".
Use the "mkboot" command to initialize the LIF area.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf

Same for lvol2 & 3

 

Any idea how to rememdy this?

 

Tariq

8 REPLIES 8
Highlighted
Torsten.
Acclaimed Contributor

Re: Mirroring a root disk on a VPAR

You need to populate the LIF area, see

 

When_Good_Disks_Go_Bad_WP
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf

 

 

But this depends on the hardware platform (RISC vs. Integrity)

 

The only difference in a vpar is, you need tp specify "/stand/vpmon" instead of "/stand/vmunix" in the autofile.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
EU-Admins-UNIX
Regular Advisor

Re: Mirroring a root disk on a VPAR

It is a PA-RISC system running 11.31

 

Here is a vparstatus

 

root@hathor at / =>vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes   Kernel Path             Opts
============================== ===== ============ ======================= =====
hathor                         Up    Dyn,Auto,Nsr /stand/vmunix
itrent                         Up    Dyn,Auto,Nsr /stand/vmunix

[Virtual Partition Resource Summary]
                                CPU      Num   Num     Memory Granularity
Virtual Partition Name          Min/Max  CPUs  IO       ILM         CLM
==============================  =======  ====  ====  ==========  ==========
hathor                            1/  8     4    13         128         128
itrent                            1/  8     1    13         128         128

                                                  Memory (MB)
                                          ILM                     CLM
                                # User                  # User
Virtual Partition Name          Ranges/MB     Total MB  Ranges/MB     Total MB
==============================  ======================  ======================
hathor                            0/   0         32768    0/   0             0
itrent                            0/   0         20672    0/   0             0

 

Here is a lvlnboot -v

 

root@hathor at / =>lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
        /dev/disk/disk124 -- Boot Disk
        /dev/disk/disk141
Boot: lvol1     on:     /dev/disk/disk124
                        /dev/disk/disk141
Root: lvol3     on:     /dev/disk/disk124
                        /dev/disk/disk141
Swap: lvol2     on:     /dev/disk/disk124
                        /dev/disk/disk141
Dump: lvol2     on:     /dev/disk/disk124, 0

lvlnboot: LIF information corrupt or not present on  "/dev/disk/disk337".
Use the "mkboot" command to initialize the LIF area.
Boot Definitions for Volume Group /dev/vg_snap_rorwork_bi:
Physical Volumes belonging in Root Volume Group:
        /dev/disk/disk337 -- Boot Disk
        /dev/disk/disk339
No Boot Logical Volume configured
No Root Logical Volume configured
No Swap Logical Volume configured
No Dump Logical Volume configured

 

Here is a lifls -l /dev/disk/disk124

 

root@hathor at / =>lifls -l /dev/disk/disk124
volume ISL10 data size 7984 directory size 8 09/01/11 13:49:28
filename   type   start   size     implement  created
===============================================================
ISL        -12800 584     242      0          09/01/11 13:49:28
AUTO       -12289 832     1        0          09/01/11 13:49:28
HPUX       -12928 840     1024     0          09/01/11 13:49:28
PAD        -12290 1864    1468     0          09/01/11 13:49:28
LABEL      BIN    3336    8        0          11/11/13 06:11:16

 

I'm very weary about using these boot commands.

 

Please advise.

 

Regards

 

Tariq

Highlighted
Torsten.
Acclaimed Contributor

Re: Mirroring a root disk on a VPAR

The system tells about disk124, disk141 and disk337.

 

Please provide

 

# vgdisplay -v vg00

 

 

Now do

 

mkboot -l /dev/rdisk/disk141

mkboot -a "hpux /stand/vpmon -a" /dev/rdisk/disk141

 

The check again with

 

# lvlnboot -v

 

and "lifls".


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
EU-Admins-UNIX
Regular Advisor

Re: Mirroring a root disk on a VPAR

root@hathor at /usr/local/scripts =>vgdisplay -v vg00
--- Volume groups ---
VG Name                     /dev/vg00
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      12
Open LV                     12
Max PV                      16
Cur PV                      2
Act PV                      2
Max PE per PV               4384
VGDA                        4
PE Size (Mbytes)            32
Total PE                    8750
Alloc PE                    8348
Free PE                     402
Total PVG                   0
Total Spare PVs             0
Total Spare PVs in use      0
VG Version                  1.0
VG Max Size                 2192g
VG Max Extents              70144

   --- Logical volumes ---
   LV Name                     /dev/vg00/lvol1
   LV Status                   available/syncd
   LV Size (Mbytes)            1792
   Current LE                  56
   Allocated PE                112
   Used PV                     2

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

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

   LV Name                     /dev/vg00/coinsadmin
   LV Status                   available/syncd
   LV Size (Mbytes)            10240
   Current LE                  320
   Allocated PE                640
   Used PV                     2

   LV Name                     /dev/vg00/scratch
   LV Status                   available/syncd
   LV Size (Mbytes)            20480
   Current LE                  640
   Allocated PE                1280
   Used PV                     2

   LV Name                     /dev/vg00/lvol4
   LV Status                   available/syncd
   LV Size (Mbytes)            40960
   Current LE                  1280
   Allocated PE                2560
   Used PV                     2

   LV Name                     /dev/vg00/lvol5
   LV Status                   available/syncd
   LV Size (Mbytes)            9216
   Current LE                  288
   Allocated PE                576
   Used PV                     2

   LV Name                     /dev/vg00/lvol6
   LV Status                   available/syncd
   LV Size (Mbytes)            2048
   Current LE                  64
   Allocated PE                128
   Used PV                     2

   LV Name                     /dev/vg00/lvol7
   LV Status                   available/syncd
   LV Size (Mbytes)            5280
   Current LE                  165
   Allocated PE                330
   Used PV                     2

   LV Name                     /dev/vg00/lvol8
   LV Status                   available/syncd
   LV Size (Mbytes)            8736
   Current LE                  273
   Allocated PE                546
   Used PV                     2

   LV Name                     /dev/vg00/oatmp
   LV Status                   available/syncd
   LV Size (Mbytes)            5120
   Current LE                  160
   Allocated PE                320
   Used PV                     2

   LV Name                     /dev/vg00/l_pgtmp
   LV Status                   available/syncd
   LV Size (Mbytes)            19456
   Current LE                  608
   Allocated PE                1216
   Used PV                     2


   --- Physical volumes ---
   PV Name                     /dev/disk/disk124
   PV Status                   available
   Total PE                    4375
   Free PE                     201
   Autoswitch                  On
   Proactive Polling           On

   PV Name                     /dev/disk/disk141
   PV Status                   available
   Total PE                    4375
   Free PE                     201
   Autoswitch                  On
   Proactive Polling           On

 

When I enetered the command

 

mkboot -l /dev/rdisk/disk141

 

I got the following, so I said no and proceeded no further..

 

root@hathor at /usr/local/scripts =>mkboot -l /dev/rdisk/disk141
There appear to be non-boot logical volumes on this device.
Overwriting them could destroy all the data on this device
Should the logical volumes be overwritten [y/n]? n
Please answer yes or no. Should the logical volumes be overwritten [y/n]? no

 

If I said yes, would I have to re-mirror all the LVs again?

Highlighted
Torsten.
Acclaimed Contributor

Re: Mirroring a root disk on a VPAR

Please show

lifls -l /dev/disk/disk141

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
EU-Admins-UNIX
Regular Advisor

Re: Mirroring a root disk on a VPAR

root@hathor at /usr/local/scripts =>lifls -l /dev/disk/disk141
volume disk14 data size 29 directory size 1 11/11/22 10:11:03
filename   type   start   size     implement  created
===============================================================
LABEL      BIN    8       8        0          11/11/22 10:11:03

Highlighted
Torsten.
Acclaimed Contributor

Re: Mirroring a root disk on a VPAR

Based on the warning you received I would remove the mirror from disk141, reduce it from vg00, pvcreate -f -B ... it again and start over to mirror (based on the document - see appendix - I sent you earlier).

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Highlighted
EU-Admins-UNIX
Regular Advisor
Solution

Re: Mirroring a root disk on a VPAR

Thanks

 

All re-mirrored and bootable...

 

lvlnboot -v


Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
        /dev/disk/disk124 -- Boot Disk
        /dev/disk/disk141 -- Boot Disk
Boot: lvol1     on:     /dev/disk/disk124
                        /dev/disk/disk141
Root: lvol3     on:     /dev/disk/disk124
                        /dev/disk/disk141
Swap: lvol2     on:     /dev/disk/disk124
                        /dev/disk/disk141
Dump: lvol2     on:     /dev/disk/disk124, 0

lvlnboot: LIF information corrupt or not present on  "/dev/disk/disk337".
Use the "mkboot" command to initialize the LIF area.
Boot Definitions for Volume Group /dev/vg_snap_rorwork_bi:
Physical Volumes belonging in Root Volume Group:
        /dev/disk/disk337 -- Boot Disk
        /dev/disk/disk339
No Boot Logical Volume configured
No Root Logical Volume configured
No Swap Logical Volume configured
No Dump Logical Volume configured

 

Not quite sure what disk337 is doing here, it's justa snap copy of production.

 

lifls -l /dev/disk/disk141


volume disk14 data size 7984 directory size 8 11/11/22 10:11:03
filename   type   start   size     implement  created
===============================================================
ISL        -12800 584     242      0          10/01/14 23:54:53
AUTO       -12289 832     1        0          10/01/14 23:54:53
HPUX       -12928 840     1024     0          10/01/14 23:54:53
PAD        -12290 1864    1468     0          10/01/14 23:54:53
LABEL      BIN    3336    8        0          11/11/23 09:42:57

 

Thanks for your help.