Operating System - HP-UX
1837230 Members
2197 Online
110115 Solutions
New Discussion

serviceguard and file systems

 
anat heilper
Frequent Advisor

serviceguard and file systems

Hi,
I'm running serviceguard 11.17 on hpux11.23 2 node cluster.
I've defined file systems to be a part of my packages. Does serviceguard list the file system on the fstab? for some reason I find some of my file systems that belong to serviceguard on teh /etc/fstab and some don't.
Is this valid situation?
Thanks,
Anat
4 REPLIES 4
likid0
Honored Contributor

Re: serviceguard and file systems

Nope, its not valid, the lvols-filesystems you have in your service guard package configuration, cant be in your /etc/fstab.

You should delete the filesystems that are configured in serviceguard from fstab


Bye
Windows?, no thanks
melvyn burnard
Honored Contributor

Re: serviceguard and file systems

The only reason that any file systems useed in any SG package should appear in the /etc/fstab file is for documentation/troubleshooting/admin purposes, but they MUST be comented out.

Example:
##The following file systems bnelong to SG package pkg1.
##Do NOT mount them manually!
#/dev/vgpatch/lvol1 /patches vxfs delaylog 0 2
#/dev/vgpatch/lvol2 /patches/OLD vxfs delaylog 0 2
#/dev/vgpatch/jobs /JOBS vxfs delaylog 0 2
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Ivan Krastev
Honored Contributor

Re: serviceguard and file systems

When SG starts package on one of the cluster, he will try to mount file systems listed in package configuration file. If these fs are already mounted via fstab, the package will fail to start.
This is the reason for removing shared VG from fstab and put them into package config file.

regards,
ivan
Stephen Doud
Honored Contributor

Re: serviceguard and file systems

Serviceguard uses package control scripts (not package configuration file as previously stated) to activate the resources such as file systems, needed by the critical applications which are also started by the package control script (directly or indirectly).
The package control script typically resides in the package directory - both of which the cluster administrator (you) create.

So, think of Serviceguard as another run level that controls the system resources needed by the critical application packages.
You don't want Serviceguard-controlled resources to be activated during boot time, because that would prevent another server from managing those resources if this server should fail. Remember, Serviceguard is a virtual server environment. Therefore, you don't want any Serviceguard controlled file systems listed in /etc/fstab, unless they are commented out, and used for reference only (as per Melvyn's comments).


You will register the LVM Volume Groups and file systems in the package control script and copy that script (along with the rest of the package directory) to the other adoptive nodes.

May I suggest that you take advantage of the current Managing Serviceguard manual, located via this link:
http://docs.hp.com/en/ha.html#Serviceguard