Mount option when configuring MCSG package

[Darius Shafie]

When configuring a package for MCSG and performing the filsystem mount configurations what are the available mount options?

[Court Campbell]

It really depends on the filesystem. But I will assume you are using vxfs. You can get read about the options via

# man mount_vxfs

[Darius Shafie]

I was thinking of that. So in SAM I just put in a if I want to mount all filesystems?

[Darius Shafie]

Or do I put in -a as if I were issuing the command?

[Court Campbell]

>So in SAM I just put in a if I want to mount all file systems?

I do not follow what you are asking.

[David Bellamy]

darius all mount commands for the package should be put in the package cntl file. ServiceGuard will mount them for you

[Darius Shafie]

I am using the Package Configuration menu of SAM to configure these packages. In the specify control script timeouts, Volume Groups, IPs... configuration option Im selecting a vg and then selecting a file system in the vg. Next I modify the filesystem options to have it mount in a specific directory, however there are two fields that you have to complete on field is the directory where you want to mount it and the other is the mount option. The help file on this window does not mention what are the mount options. I looked up the options for the mount command and -a mounts all filesystems. However in the command you actually type -a. In SAM I've tried -a and a. In both case the package is created but when I try to start the package it fails. If I just configure the package without specifying a mount directory then I can create and start the package. So Im thinking that neither -a nor a is the correct mount option to use in SAM.

Now has anyone configured a package via SAM, and do they know what the mount options are for SAM?

Here is the output in control.sh.log

######## Node "hp9000": Starting package at Fri Jul 20 09:33:48 EDT 2007 ###########
Jul 20 09:33:48 - "hp9000": Activating volume group /dev/vgcls2 with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "/dev/vgcls2" has been successfully changed.
Jul 20 09:33:49 - Node "hp9000": Checking filesystems:
/dev/vgcls2/cls2
file system is clean - log replay is not required
Jul 20 09:33:49 - Node "hp9000": Mounting /dev/vgcls2/cls2 at /cls2
usage: mount [-l][-v|-p]
mount [-F FStype][-eQ] -a
mount [-F FStype][-eQrV][-o specific_options]
{ special | directory }
mount [-F FStype][-eQrV][-o specific_options]
special directory
ERROR: Function check_and_mount
ERROR: Failed to mount /dev/vgcls2/cls2
Jul 20 09:33:49 - Node "hp9000": Deactivating volume group /dev/vgcls2
Deactivated volume group in Exclusive Mode.
Volume group "/dev/vgcls2" has been successfully changed.

########### Node "hp9000": Package start failed at Fri Jul 20 09:33:49 EDT 2007 ###########

[PeterWolfe · Accepted solution]

You want the mount options just for
the specific filesystems in your package.
foo example:

-o rw,largefiles

for a VxFS filesystem with largefile support.
Note that you do specify the -o. The package
line would be:

FS_MOUNT_OPT[0]="-o rw,largefiles"

[PeterWolfe]

Also, you might like using Serviceguard
Manager more than SAM. Serviceguard Manager
is a GUI and available from
software.hp.com:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B8325BA

You didn't mention what version of Serviceguard
you are using. In the latest versions
of Serviceguard, Serviceguard Manager is bundled. This new version is plug-in for System Management Homepage
(which is the web-based SAM follow-on).
The software.hp.com version is the
standalone version.

[Darius Shafie]

Hi Peter,

Is that a -0(zero) or -o(lowercase 0) that I put in the mount option field?

Thanks,
Darius.

[A. Clay Stephenson]

This is why it is important to visit the man pages; you would then know that "o" is a lower-case letter o.

By the way, using SAM or a configuration manager should only be used AFTER you know how to do all the tasks manually. This applies to essentially all tasks: adding users, building volume groups, configuring SG, building kernels, ... . While taking this approach requires that you know more, it also greatly improves you overall skills and especially your troubleshooting skills.

[Darius Shafie]

I did visit the man pages and it is a lowercase o. Anyhow, using that option I still get the same error as I had mentioned above.

[Darius Shafie]

Clay,

Also if I had access to documentation that gave me specific instructions on how to perform these tasks, I'm sure I wouldn't be using this forum as much as I am.

Since the previous guy who had my job seems to have taken home with him both software and manuals, I don't have the luxury of referring to manuals to learn the process by which to configure MCSG and its packages via commands.

Everything I've learned about HPUX thus far has been via visiting various web sites, this forum and the man pages.

Considering that I've learned how to install the OE, configure the networking, permissions, access rights, and configuring MCSG up to to this point without any docs using the methods I listed above I think Im coming along, its just that some problems I face I can't find the proper document that explains it or helps troubleshoot it.

Thanks for your input!

[A. Clay Stephenson]

Almost all documentation is available for free at docs.hp.com. You can download, print, and bind the manuals and have a complete set for reference. The part you are missing by relying upon facilities like SAM is the most critical part of an SG cluster -- robustness. Actually creating an SG cluster and packages is rather easy. In fact, an experienced admin can create a cluster (from the standpoint of installing the software, running the LVM commands, running the cmxxxxx commands) very quickly. The hard part is making a robust cluster so that failures of hardware, networks, disks, power, HVAC is handled without significant impact. Unless you do those things (especially networks), you can actually wind up with a cluster that is a less reliable than a standalone system.

[Darius Shafie]

Clay,

I did as you suggested. I found HP doc B3936-90073 and read the part concerning the packages.

I don't why this made a difference but when Im using SAM configures the control.sh script in the following manner:

LV[0]=
FS[0]=
FS_MOUNT_OPT[0]=
FS_UMOUNT_OPT[0]=

Two things there were not "" around the parameters, and they were no ;

I edited the control script so that it was all on one line seperated by ; and put "" around the parameters, like so:

LV[0]=””;FS[0]=””;FS_MOUNT_OPT[0]=””;FS_UMOUNT_OPT[0]=””

I then distributed the file to both nodes and started the package in SAM. Worked like a charm.