Volume is mounted on two ServiceGuard nodes


 
Thread Tools Search this Thread
Operating Systems Linux Volume is mounted on two ServiceGuard nodes
# 1  
Old 02-21-2014
Volume is mounted on two ServiceGuard nodes

Hey! I'm running a HP ServiceGuard cluster with three nodes. One of the packages was moved (not by me) from one node to another a few weeks ago.

I just noticed that one of the volume groups is still mounted on the old node. Oops! When I run df, less space is used on the old node than the new.

What's the safest way to get rid of it on the old node with no corruption? Off the top of my head I'm thinking something along the lines of:

Code:
mount -oremount,ro VOLUME
umount VOLUME
vgchange -an VOLUME_GROUP

Any tips? Thanks!
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

2. Solaris

In Solaries 10 how to mount multiple volume on same mounted point

Hi , I am completely stuck and not getting any clue to come out this . So looking for help Q : I have salaries 10 in server with that Dell Equallogic storage connected. in dell Equlalogic in i have 70 TB storage . I created 7 volumes 10 TB each . In Solaries 10 i have syslog server i... (1 Reply)
Discussion started by: Roahn Tiwari
1 Replies

3. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

4. HP-UX

MC Serviceguard and WebSphere ND 6.1

I am a Lawson Software consultant assisting a client with a Lawson upgrade. One of our components is WebSphere Application Server ND 6.1. Our client is using MC Serviceguard for failover. When testing failover, my Websphere instance is trying to start, but generating this error, referencing the old... (4 Replies)
Discussion started by: mrvitas
4 Replies

5. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

6. HP-UX

ServiceGuard cluster & volume group failover

I have a 2-node ServiceGuard cluster. One of the cluster packages has a volume group assigned to it. When I fail the package over to the other node, the volume group does not come up automatically on the other node. I have to manually do a "vgchange -a y vgname" on the node before the package... (5 Replies)
Discussion started by: Wotan31
5 Replies

7. UNIX for Advanced & Expert Users

Ownership problem using a CIFS-mounted volume

Hello, I am trying to use a storage service for backing large amounts (terabytes) of data. The service uses Linux machines and allows mounting of their disks using the CIFS/SMB protocol. I do have the option of using rsync directly over the network without mounting. But in order to... (4 Replies)
Discussion started by: same1290
4 Replies

8. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies

9. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
Login or Register to Ask a Question
cmcheckconf(1m) 														   cmcheckconf(1m)

NAME
cmcheckconf - check high availability cluster configuration and/or package configuration files SYNOPSIS
cmcheckconf [-v] [[-k|-K] -C cluster_ascii_file] [[-p pkg_reference_file] | [-P pkg_ascii_file]...] DESCRIPTION
cmcheckconf verifies the cluster configuration as specified by the cluster_ascii_file and/or the package configuration files specified by each pkg_ascii_file in the command. If the cluster has already been configured previously, the cmcheckconf command will compare the con- figuration in the cluster_ascii_file against the previously configuration information stored in the binary configuration file and validates the changes. The same rules apply to the pkg_ascii_file. It is not necessary to halt either the cluster or any of the packages to run the cmcheckconf command. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can verify the configuration. cmcheckconf verifies any configured external script program in each pkg_ascii_file for the package run and halt function by calling it with a "validate" parameter. A non-zero return value from any external script program will cause the command to fail. If the cluster_ascii_file specifies a quorum server as the cluster tie-breaker service, the quorum server must be running and all nodes in the cluster configuration must be authorized to access it. If more than one IP address is specified for the quorum server, the quorum server must be reachable from all configured nodes through all the IP addresses. Otherwise the cmcheckconf command will fail. If the cluster_ascii_file specifies the lock lun devices as the cluster tie breaking service, all nodes must be accessing the same physical device. The lock lun device file must be a block device file. The cluster must be down before you can modify a cluster tie-breaking ser- vice. Options cmcheckconf supports the following options: -v Verbose output will be displayed. -k Using the -k option means that cmcheckconf only checks disk connectivity to the LVM volume group that are identified in the ASCII file. This option does not exist on Linux. Omitting the -k option (the default behavior) means that cmcheckconf tests the connectivity of all LVM volume groups on all the cluster nodes. Using -k can result in significantly faster operation of the command. -k must be used with -C and can not be used with -K -K Using the -K option means that cmcheckconf only checks disk connectivity for cluster lock volume groups. For all other LVM volume groups no connectivity will be checked. This option does not exist on Linux. Omitting the -K option (the default behavior) means that cmcheckconf tests the connectivity of all LVM volume groups on all the cluster nodes. Using -K can result in significantly faster operation of the command. -K can be used only when cluster is already configured and is used with -C -K can not be used with -k. -C cluster_ascii_file Name of the cluster ASCII file to use. This file can be created by either the cmquerycl command or cmgetconf command. See cmquerycl(1m) or cmgetconf(1m). This is a required parameter if the cluster has never been configured before. If not specified, the local cluster configuration is used. -P pkg_ascii_file... Name of the package configuration file(s) to use. A package configuration template file can be created by using the cmmakepkg command and must be customized to include specific information for the package. See cmmakepkg(1m). A configu- ration file for an existing package can be generated by using the cmgetconf command. See cmgetconf(1m). Once a package configuration file is generated from the existing configuration using cmgetconf, it can be modified to reflect the desired changes for that package. The package configuration file will be scanned for the purpose of validation. -p pkg_reference_file Name of the file containing a list of package configuration file(s) to be used. This file may be necessary if the number of pkg_ascii_file names given with multiple -P options do not fit on the command line. This option cannot be used with the -P option. RETURN VALUE
Upon completion, cmcheckconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains an ASCII cluster configuration file, and two packages, pkg1 and pkg2, specified in ASCII files pkg1.config and pkg1.config. To verify the cluster configuration and package files, do the following: cmcheckconf -C clusterA.config -P pkg1.config -P pkg2.config To verify the cluster configuration while restricting the connectivity check to the volume groups specified in the clusterA.config file, cmcheckconf -k -C clusterA.config -P pkg1.config -P pkg2.config To verify the cluster configuration while restricting the connectivity check to the cluster lock volume groups, cmcheckconf -K -C clusterA.config -P pkg1.config -P pkg2.config To specify a long list of package configuration files do the following: cmcheckconf -C clusterA.config -p myfile where myfile contains: pkg1.config pkg2.config pkg3.config The cluster is up and running, with both packages pkg1, pkg2 running as well. The package configuration file pkg1.config contains the changes to the package pkg1. To verify the package configuration changes made for pkg1, do the following: cmcheckconf -P pkg1.config AUTHOR
cmcheckconf was developed by HP. SEE ALSO
cmapplyconf(1m), cmdeleteconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmcheckconf(1m)