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
cmhaltpkg(1m)															     cmhaltpkg(1m)

NAME
cmhaltpkg - halt a high availability package SYNOPSIS
cmhaltpkg [-v] [-t] [-n node_name]... package_name... cmhaltpkg [-v] [-s] [-n node_name]... package_name... DESCRIPTION
cmhaltpkg connects to the Serviceguard cluster manager and halts the specified package(s) or multi-node package instance(s). When a package or package instance is halted, global switching (AUTO_RUN) is disabled for that package. cmhaltpkg may be run on any node within the cluster and may operate on any package within the cluster. To halt a package, a user must either be a superuser with effective user ID of zero (see id(1) and su(1)), or have an access policy of PACKAGE_ADMIN allowed in the cluster or package configuration file. See access policy in cmquerycl(1m) or cmmakepkg(1m). If no node_name arguments are supplied, each package will be halted on any and all nodes where it is running. If the package is not running on any nodes, the command will fail. cmhaltpkg should not be used to halt SYSTEM_MULTI_NODE packages (HP-UX only). Use cmhaltnode or cmhaltcl to halt SYSTEM_MULTI_NODE packages instead. Packages of other types may be halted on a subset of the configured nodes by specifying one or more node_name arguments. cmhaltpkg will fail if each specified package is not running on all the specified nodes. Packages are halted in the order required by their configured dependencies. Packages without configured dependencies are halted in the order specified on the command line. To successfully halt a package, all required dependent packages must either be previously halted or specified as a package_name argument in the cmhaltpkg command. Packages configured with STORAGE_GROUP are implicitly dependent on the cor- responding multi-node cluster volume manager (CVM) package. (HP-UX only) cmhaltpkg validates its command line prior to halting any package and returns an error if the user does not have correct access to complete the operation or if illegal combinations of node_name and package_name arguments are encountered. If a problem is detected while halting a package, cmhaltpkg exits with an error indication and remaining package_name arguments are not processed. A package in maintenance mode that was start up to and including a specified module can be halted from that specified module. Only those modules which were started are halted. Options cmhaltpkg supports the following options: -n node_name Acts only on a specific node. If the package is not running on the specified node, it will not be halted. -v Verbose output will be displayed. -t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or pack- ages. This option validates the node's eligibility with respect to the package dependencies as well as the external dependencies such as EMS resources, package subnets, and storage before predicting any package placement decisions. This option is not legal for package in maintenance mode. -s Symmetric halt is only for packages in maintenance mode. If a package in maintenance mode has been started up to a module as specified by cmrunpkg -m, then cmhaltpkg -s will halt the package up to that module. Otherwise, cmhaltpkg -s will halt the package for all the modules specified in its configuration file. RETURN VALUE
cmhaltpkg returns the following value: 0 Successful completion. 1 Command failed. 2 Command failed due to a transient condition. EXAMPLES
A sequence of cmhaltpkg and cmrunpkg commands may be used to move a package from one node to another. For example, the package may be halted on one node and then run on a new node, provided that the package is enabled for the new node. To move package package1 to node node2, do the following: cmhaltpkg package1 cmrunpkg -n node2 package1 cmmodpkg -e package1 (to enable package switching, if desired) AUTHOR
cmhaltpkg was developed by HP. SEE ALSO
cmmakepkg(1m), cmquerycl(1m), cmmodpkg(1m), cmrunpkg(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmhaltpkg(1m)