lifls different on mirrored boot disks

[mghosalk]

Hello,

After creating a mirrored boot disk as per steps in LVMKBRC00005103, lifls is show one missing file in the primary disk.

(from primary disk)
# lifls /dev/rdsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL

(from newly mirrored disk)
# lifls /dev/rdsk/c2t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO ISL AUTO
HPUX PAD LABEL


The PAD file was never there on the primary disk even before the mirror was added.

Steps for mirroring shown below:
#pvcreate -B /dev/rdsk/c2t6d0
#vgextend /dev/vg00 /dev/dsk/c2t6d0
#mkboot -l /dev/rdsk/c2t6d0
#mkboot -a "hpux -lq" /dev/rdsk/c2t6d0
#mkboot -a "hpux -lq" /dev/rdsk/c1t6d0

#for i in 1 2 3 4 5 6 7 8
do
lvextend -m 1 /dev/vg00/lvol${i} /dev/dsk/c2t6d0
done


#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2
#lvlnboot -v


# lifls /dev/rdsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL

# lifls /dev/rdsk/c2t6d0
ISL AUTO HPUX PAD LABEL

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t6d0

# lifls /dev/rdsk/c2t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO ISL AUTO
HPUX PAD LABEL

# lifls /dev/rdsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL


Thanks
Mandar

[Sridhar Bhaskarla · Accepted solution]

Hi Mandar,

You can run "mkboot -b /usr/sbin/diag/lif/updatediaglif2..." command on the primary disk also to update the offline diagnostics. That should sync up the utilities.

Make sure you run your "lvlnboot" commands after any mkboot command.

-Sri

[Kevin Wright]

jut run the same mkboot command on your boot disk.
mkboot -b /usr/sbin/diag/lif/updatediaglif2

but use -P PAD.

[mghosalk]

Sridhar Kevin,

even after using mkboot on the primary disk preserving the existing lif files on it did not create PAD file on the primary. Read on some other post that PAD file is for padding the free space in the boot area.

1. am i correct in assuming that PAD need not/does not get sync'ed with mkboot -b updatedialif2?

2. does PAD need to be sync'ed between the two mirror boot disks?

3. if yes on 2 then how to sync it ? using mkboot -i ???

this is what i did
***************************
# mkboot -b /usr/sbin/diag/lif/updatediaglif2 > -p AUTO -p CONFIGDATA -p HPUX -p IOTEST2 -p ISL -p LABEL -p MAPFILE -p MAPPER2 -p ODE > -p PERFVER2 -p PVCU -p SLDEV2 -p SLDRV2 -p SLMOD2 -p SLSCSI2 -p SSINFO -p SYSLIB /dev/rdsk/c1t6d0
# lifls /dev/rdsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO AUTO HPUX
ISL LABEL
# lvlnboot -r /dev/vg00/lvol3
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
# lvlnboot -b /dev/vg00/lvol1
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
# lvlnboot -s /dev/vg00/lvol2
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
# lvlnboot -d /dev/vg00/lvol2
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
# lifls /dev/rdsk/c1t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO AUTO HPUX
ISL LABEL
# lifls /dev/rdsk/c2t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO ISL AUTO
HPUX PAD LABEL

***************************
Thanks
Mandar

[Michael Steele_2]

The bootlif is 2 mb and the pad is left over, unused space. If you use 'lifls -l' a more detailed report of the bootlif is displayed.

# lifls -l /dev/dsk/c1t6d0

Also, note the 'distribution of physical volume' with pvdisplay, i.e,

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 21 21
/dev/vg00/lvol2 256 256
/dev/vg00/lvol3 35 35
/dev/vg00/lvol4 384 384

[mghosalk]

Michael,

Is it safe to remove the PAD file from the mirror disk?

Thanks
Mandar

[Kevin Wright]

Doesn't sound like it's anything to worry about, if both disks are bootable and sync'd, you should be fine.

[Sridhar Bhaskarla]

HI Mandar,

YOu do not need to worry about PAD. As explained by Michael, it is only the left over space. You will see the differences in sizes of these lif files if you use "-l" option with lifls.

Basically you preserved (-p option) ISL, AUTO, HPUX etc., on c2t6d0. So, they will be left untouched and other offline diagnostics will be updated. So, you will find the date stamps (lifls -l) and sizes match for both the disks except the ones you specified with -p.

-Sri

[mghosalk]

Guys,

Thanks for your posts.
Looks like i dont need to worry. Also i successfully "bo alt".

Thanks,
Mandar