Operating System - HP-UX
1837836 Members
2472 Online
110121 Solutions
New Discussion

vg not active after reboot

 
SOLVED
Go to solution
Peter Jenssen
Advisor

vg not active after reboot

Hi,
I'm new to HPUX, so this might have a trivial solution :-)

I have added a new disk to a system that is a member of a cluster.
The disk is an exported LUN from a Hitachi SAN.
(as is all disk on this cluster)

Everything went well, I created volume group vg02 (vg00 is system disks, vg01 is shared between cluster members), I
created a filesystem on it and mounted it without problem.

-However, after reboot, vg02 is never activated.
Mounting it of course doesn't work,
but after a vgchange -a y /dev/vg02
it mounts fine.

Is there a way of fixing this that I have missed?
I don't think you should have to do a
vgchange -a y /dev/vg02 after every reboot?


thanks,

Peter Jenssen
4 REPLIES 4
Michael Tully
Honored Contributor

Re: vg not active after reboot

I would say because it is because it is in a cluster environment. (I don't have one to try)

You could create a simple script that runs during startup to activate the volume group. Have it in /sbin/init.d with a link to the startup directory, say /sbin/rc3.d/S990vg02start
Anyone for a Mutiny ?
Sridhar Bhaskarla
Honored Contributor
Solution

Re: vg not active after reboot

Hi Peter,

It's a common practice for the SAs to customize /etc/lvmrc on the clustered systems so that only vg00 and other volume groups specified under that file would be enabled. Rest are meant to be taken care by serviceguard but they have to be made cluster aware by the command 'vgchange -c y' while the cluster is running.

Since you added a new volume group, you may need to add it to your /etc/lvmrc file. Look at the file. It's easily understandable.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Peter Jenssen
Advisor

Re: vg not active after reboot

Thanks!
Adding /sbin/vgchange -a y /dev/vg02
to custom_vg_activation()
fixed it!

Great!

Peter
Ralf Seefeldt
Valued Contributor

Re: vg not active after reboot

Hello Peter,

you used vgchange -a y to activate the vg for anny access.

If the vg is part of a clusterpackage, you should think about using
vgchange -a e to activate it exclusively for 1 single server. This server may export it again, but in this way, no other server/client can write to that vg when the clusterpackage may be down.
This may be essentill e.g. with databases.

Regards
Ralf