mirroring root FS and primary swap

[Olga_1]

m trying to mirror root FS and primary swap, when I do
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c2t6d0
I get the following output:
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: Boot volume should be the first logical volume on the physical volume

Is this lvlnboot message an error? di I do something wrong?

Thank you for your comments.

[Helen French · Accepted solution]

Hi Olga:

This is just a message. IF you suspect any problem, check it with:

# lvlnboot -v

Check the sequence of LVs in this listing also in here:

# pvdisplay -v /dev/dsk/c2t6d0
HTH,
Shiju

[James R. Ferguson]

Hi:

The problem is that you need mirror the logical volumes in the order lvol1, lvol2, lvol3. The remaining ones do not matter, but I think a good standard is to do them in order. See the man pages for 'lvlnboot' for more information.

Regards!

...JRF...

[Uday_S_Ankolekar]

This is just informations for you. Are you sure you have primary swap on lvol1?? Usually it should be on lvol2

Check with lvlnboot -v and lvsiaplay -v /dev/vgnn/lvolnn should show you both primary disk and alternate disk as current

-USA..

[Mark Greene_1]

potentially an error if lvol1 is not the first physical volume on the disk. See this thread:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc85663ce855d511abcd0090277a778c,00.html

you can verify with lvdisplay -v [lv_path]|pg
and see how many mirror copies it reports.

And then you can do pvdisplay -v [disk]|pg using the pvinfo from the output of the lvdisplay and see what order the lvols are in.

HTH
mark

[Olga_1]

Thank you all, I will re-do them in order.

[Helen French]

Hi Olga:

Again, If you suspect the problem in the order you mirrored the LVs (lvol1, lvol2, lvol3), then check it with lvlnboot -v before you reboot. Also check this document (TKB #KBRC00001462) about the same error:

http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000048319683

HTH,
Shiju

[Sanjay_6]

Hi Olga,

You cannot extend the size of / and primary swap without reloading the OS because they should be spread over contiguous extents. You have to take a ignite backup of the system and reload the OS on this system to increase the size of / and primary swap.

Hope this helps.

regds

[Sanjay_6]

Hi Olga,

I'm sorry, i didn't understand your question clearly. I thought you were trying to increase the size of /. What you are trying to do is mirror the roor disk. For this start from scratch on a new disk,

pvcreate -B /dev/rdsk/cxtydz
vgextend /dev/vg00 /dev/dsk/cxtydz
mkboot -l /dev/rdsk/cxtydz
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/cxtydz
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/cxtydz
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/cxtydz
lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/cxtydz

Do this for other lv's too if you have enough disk space.

Hope this helps.

Regds

P.S. : Sorry about the previous post.

[Olga_1]

I do not think that there is a need to do everything from scratch: pvcreate, etc.

All I did is lvreduce -m 0 for all lv on vg00 and then:
lvextend in the right order: lvol1, lvol2, etc.

Thank you all.

[James R. Ferguson]

Hi Olga:

As long as you correctly created the mirror boot disk ('pvcreate -B', 'mkboot', etc.) and then mirrored your logical volumes in the correct order (as indicated in my earlier post) you do *not* need to start over. Reducing the mirrors and re-mirroring the disk was the correct approach.

I trust that you also specified a "low-quorum" when you did your 'mkboot':

mkboot ???a ???hpux ???lq???

If all of the above is true, then the acid test is to boot from the disk!

Regards!

...JRF...

[Olga_1]

James,
I did:
mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c2t6d0

Should I specify -iq ?

[Helen French]

Hi Olga:

Again, it's not "iq" , it's "-lq". This for no quorum check. If you don't specify this, then when the root disk fails, for booting from the mirror root disk, you have to interrupt the boot process, then at

ISL > hpux -lq

If you specify -lq at the mkboot, then you don't need to do this. The system will automatically boot.

HTH,
Shiju

[Olga_1]

Sorry, I did mean -lq

so the right syntax is:

mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c2t6d0

Correct?

[Sanjay_6]

Hi Olga,

Yes you are correct. The right syntax for the boot string on mirror root disk is,

mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/cxtydz

Hope this helps.

Regds

[James R. Ferguson]

Hi Olga:

# mkboot ???a ???hpux ???lq??? /dev/rdsk/cXtYdZ

...will do fine.

Regards!

...JRF...

[Alan Riggs]

One clrification to the above:

You should issue the mkboot by itself first (to write the BOOTLIF area). Then issue mkboot -a to write the bot string. At least, that is how I learned the procedure way back in the dark ages.

[Mike_305]

Hi Olga,

Here the script will do it all.

THX - Mike