Sponsored Content
Operating Systems AIX Sysmirror 7.1.3 Resource Group NFS mounts Post 303001313 by bakunin on Tuesday 1st of August 2017 01:49:16 PM
Old 08-01-2017
Quote:
Originally Posted by MichaelFelt
Something else to look into (bakunin please verify still possible - I do not have a PowerHA/SystemMirror config to review) would be to remove the mount/unmount from the start/stop scripts.

Instead, make the mounts part of the resource group - and the resource group makes sure the mounts are active before calling the start script and the unmounts are called after the stop script.
Absolutely!

Right now i don't have a HACMP-system at hand to check the details myself, but: yes, that is (still) possible and in fact is the recommended way to do it.

Mounts will be done by a sort-of start/stop-Script HACMP provides for itself, its name is "clas-nfsv4" or something similar (again, i can't check and am working from memory) which will be entered automatically when you configure an NFS-mount and/or -export. I am not sure if one can configure the order in which this and your own application-server is called but if you want to be perfectly sure configure the NFS-services in its own RG, then configure a start before/stop after-dependency with your application RG.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

NFS mounts and user permissions

We need to allow ordinary users to preform NFS mounts on a AIX server without giving them root access to the server. Is there a way to give an ordinary users root access on a tem basis or a script to allow them to preform NFS mounts? (4 Replies)
Discussion started by: daveisme
4 Replies

2. Solaris

Could I re-export a NFS resource to a third server ?

Hey Guys. Could someone said if is possible take a NFS resource get it from a original Server a export it and mount it in a third server ? Thank in Advace.... SUN ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies

3. Solaris

NFS resource goes down frecuently in solaris zone

Hi guys. We have filesystems resources taken from tha NAS nettap ; but the filesystem inside the solaris zone with some frecuency is unable.This filesystems are critical and we need constantly remount them. Someone know if there are problems with the NFS resources in zones? Where are... (3 Replies)
Discussion started by: aggadtech08
3 Replies

4. AIX

Resource Group Monitoring

Hi, I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification. Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in... (2 Replies)
Discussion started by: srnagu
2 Replies

5. Solaris

Max. number of NFS mounts

Hi, I was wondering, whether there is a limit regarding the max number of nfs mounts in Oracle Solaris 10 (newest update). The data center plans to migrate from a fibre channel based storage environment (hitachi) to a nfs based storage environment (netapp). Regarding the Solaris 10 database... (1 Reply)
Discussion started by: schms
1 Replies

6. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

7. AIX

HACMP, NFS cross-mount problem. Can not move resource group

Hi, I'm new to HACMP. Currently I setup a cluster with nfs cross-mount follow this guide: kristijan.org NFS cross-mounts in PowerHA/HACMPMy cluster has two nodes: erp01 and erp02. I'm using nfs4 with filesystem for nfs is: /sapnfs Cluster start without problems. But I cannnot move RG (with... (3 Replies)
Discussion started by: giobuon
3 Replies

8. Shell Programming and Scripting

find command exclude nfs mounts

Gentleman and Ladies, I am having some difficulty in regards to the find utility. I am trying to not traverse nfs mounts when searching for files or directories. This command does not seem to work. It still returns directories that live on nfs shares. The man page says: -fstype type... (6 Replies)
Discussion started by: jaysunn
6 Replies

9. Red Hat

NFS mounts query

We have 2 servers in cluster. Node1 has an ext3 mount for backups and the other connects using NFS to this node1. I believe the reason it is configured in this manner is to not duplicate backups since this is a Database server. Not sure this was the reason though. Right now if node1 goes down all... (5 Replies)
Discussion started by: ikn3
5 Replies

10. Solaris

NFS mounts not automounting on boot

I have several Solaris 11.2 zones. when I reboot them I have to go in and do mountall to mount the NFS mounts. any ideas where to troubleshoot why they are not automounting? (2 Replies)
Discussion started by: os2mac
2 Replies
OCF_HEARTBEAT_FILESY(7) 					OCF resource agents					   OCF_HEARTBEAT_FILESY(7)

NAME
ocf_heartbeat_Filesystem - Manages filesystem mounts SYNOPSIS
Filesystem [start | stop | monitor | meta-data | validate-all] DESCRIPTION
Resource script for Filesystem. It manages a Filesystem on a shared storage medium. The standard monitor operation of depth 0 (also known as probe) checks if the filesystem is mounted. If you want deeper tests, set OCF_CHECK_LEVEL to one of the following values: 10: read first 16 blocks of the device (raw read) This doesn't exercise the filesystem at all, but the device on which the filesystem lives. This is noop for non-block devices such as NFS, SMBFS, or bind mounts. 20: test if a status file can be written and read The status file must be writable by root. This is not always the case with an NFS mount, as NFS exports usually have the "root_squash" option set. In such a setup, you must either use read-only monitoring (depth=10), export with "no_root_squash" on your NFS server, or grant world write permissions on the directory where the status file is to be placed. SUPPORTED PARAMETERS
device The name of block device for the filesystem, or -U, -L options for mount, or NFS mount specification. (required, string, no default) directory The mount point for the filesystem. (required, string, no default) fstype The type of filesystem to be mounted. (required, string, no default) options Any extra options to be given as -o options to mount. For bind mounts, add "bind" here and set fstype to "none". We will do the right thing for options such as "bind,ro". (optional, string, no default) statusfile_prefix The prefix to be used for a status file for resource monitoring with depth 20. If you don't specify this parameter, all status files will be created in a separate directory. (optional, string, default ".Filesystem_status/") run_fsck Specify how to decide whether to run fsck or not. "auto" : decide to run fsck depending on the fstype(default) "force" : always run fsck regardless of the fstype "no" : do not run fsck ever. (optional, string, default "auto") fast_stop Normally, we expect no users of the filesystem and the stop operation to finish quickly. If you cannot control the filesystem users easily and want to prevent the stop action from failing, then set this parameter to "no" and add an appropriate timeout for the stop operation. (optional, boolean, default yes) force_clones The use of a clone setup for local filesystems is forbidden by default. For special setups like glusterfs, cloning a mount of a local device with a filesystem like ext4 or xfs independently on several nodes is a valid use case. Only set this to "true" if you know what you are doing! (optional, boolean, default false) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 60. stop Stops the resource. Suggested minimum timeout: 60. notify Suggested minimum timeout: 60. monitor Performs a detailed status check. Suggested minimum timeout: 40. Suggested interval: 20. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a Filesystem resource using the crm(8) shell: primitive p_Filesystem ocf:heartbeat:Filesystem params device=string directory=string fstype=string op monitor depth="0" timeout="40" interval="20" SEE ALSO
http://www.linux-ha.org/wiki/Filesystem_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_FILESY(7)
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy