please help me to verify this information

[hi_5]

I use HP-UX to mirror / /stand and swap.
I then create a different volume group that contains tmp home usr var filesystems and use cpio to copy the information over. I then edit the /etc/fstab to reflect the change that have make to tmp home usr var because / stand and swap are still on the same volume group.
I change the primary boot path.
My questions : Do tmp home usr var have to be on vg00 in order for the system to boot?
because as I recall, the system will use /standvmuix to boot it up ...? and i can manually mount everythings up as long it is in the fstab ..
am i correct on this???

[steven Burgess_2 · Accepted solution]

Hi

The system will certainly boot with /tmp /usr and /var in seperate volume group, this however is not best practice

You have mirrored / /stand and swap. If you lose /var or other OS lvols your system will be unusable.

Are you intending using ignite to back up your root volume group ? keeping all your lvols in vg00 is a much cleaner and easier way to manage your system.

HTH

Steve

[Con O'Kelly]

Hi

No /tmp, /home, /var & /usr filesystems do not have to be on root VG.

However from the point of view of managing the OS, I would keep at least /var & /usr on root VG if space permits.
If you need extra space in /var, create seperate Filesystems (eg /var/adm/save, /var/opt/OV etc)

I try to keep all "OS" filesystems on root VG and every other FS in different VG's. I mirror the entire the root VG. It makes it easier to administer the system. This is just my philosophy, others may have a different way of doing things.

Not quite sure what you mean by manually mount. At boot time every FS listed in /etc/fstab will automatically be mounted. To manually mount a filesystem (ie using mount commnad), it does not have to be /etc/fstab.

Cheers
Con

[Michael Steele_2]

OK - I've seen your last five postings so lets pause for a moment and take inventory before answering any more questions.

Please post the results of these commands in a new message and summarize the problem, what is it? How to create a bootable LUN on a disk array?

ioscan -fnkC disk
lvlnboot -v
bdf
vgdisplay -v
set_boot -p
swapinfo -tam
ll -d /dev/*/group
strings /etc/lvmtab

[Steven E. Protter]

Standard hpux practice is to leave certain volumes as part of vg00.

Thats not the rule, its just the way most folks do it.

/var /home /usr /stand /opt are usually part of vg00.

Make it easier to take vacations following certain rules.

SEP

[hi-i]

Question : Can hp/ux boot if /tmp /home /usr and /var are on different vg?

steps : ( just summary)
pvcreate -B -f /dev/rdsk/disk
vgextend vg00 /dev/dsk/disk
mkboot /dev/rdsk/
mkboot -a "hp-lq" /dev/rdsk/disk
lvextend -m 1 lvol1
lvextend -m 1 lvol2
lvextend -m 3 lvol3
lvlnboot -b lvol1
lvlnboot -r lvol3
lvlnboot -s lvol2

Because of the useful information on this forum, I was able to mirror vg00 without any problem.

I understand with standard practice that /usr / /stand /home /var should be under vg00. Because of space is not available, I have just completed mirror / /stand and swap, and the rest , i have created a new volume group and copy it over to the new filesystems.
pvcreate -f /dev/rdsk/disk
vgcreate new volume
lvcreate logical volume tmp home usr var
using newfs to create filesystem
mount them up
cd /usr
and use this command to copy the info
find . -xdev -depth -print | cpio ... /new_tmp
- once done copy for all other volume group
- edit the fstab to reflect the change...
- base on the following info that I represent, i shouldn't have any problems booting up? the only different is now again
/tmp home usr var is on different volume...
- hope this clarify my questions, thanks for your time


# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c2t6d0 (0/0/2/1.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Root: lvol3 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0

Current bdf file

[ bdf | grep vg00
/dev/vg00/lvol3 143360 89593 50700 64% /
/dev/vg00/lvol1 83733 32165 43194 43% /stand
/dev/vg00/lvol8 1105920 806345 281608 74% /var
/dev/vg00/lvol7 1179648 938628 226015 81% /usr
/dev/vg00/lvol4 1024000 405052 581958 41% /tmp
/dev/vg00/lvol6 536576 499967 34367 94% /opt
/dev/vg00/lvol5 2097152 2063856 31251 99% /home
/dev/vg00/lvol10 512000 6990 473470 1% /apps/sys
strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0
/dev/vgroot
/dev/dsk/c16t0d3

bdf | grep vgroot
/dev/vgroot/tmp 10240000 409546 9523298 4% /new_tmp
/dev/vgroot/home 10240000 2072498 7912312 21% /new_home
/dev/vgroot/opt 2048000 500326 1450990 26% /new_opt
/dev/vgroot/usr 5120000 939554 3919227 19% /new_usr
/dev/vgroot/var 5120000 805684 4044727 17% /new_var
/dev/vgroot/sys 1024000 6949 953508 1% /new_apps

vi /etc/fstab to reflect the changes
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vgroot/tmp /tmp vxfs delaylog 0 2
/dev/vgroot/home /home vxfs delaylog 0 2
/dev/vgroot/opt /opt vxfs delaylog 0 2
/dev/vgroot/usr /usr vxfs delaylog 0 2
/dev/vgroot/var /var vxfs delaylog 0 2
/dev/vgroot/sys /apps/sys vxfs delaylog 0 2

*** These are the infos that you have requested...