Volume is mounted on two ServiceGuard nodes

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. 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...

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.

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...

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...

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...

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...

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...

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

LEARN ABOUT HPUX

cmdeleteconf

cmdeleteconf(1m)														  cmdeleteconf(1m)

NAME

       cmdeleteconf - Delete either the cluster or the package configuration

SYNOPSIS

       cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...]

DESCRIPTION

       cmdeleteconf  deletes either the entire cluster configuration, including all its packages, or only the specified package configuration.	If
       neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all  its  packages.	If
       the  local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration.	If
       only the package_name is specified, the configuration of package_name in the local cluster is deleted.	If  both  cluster_name	and  pack-
       age_name  are  specified, the package must be configured in the cluster_name, and only the package package_name will be deleted.  cmdelete-
       conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the  con-
       figuration version.  The local cluster is the cluster that the node running the cmdeleteconf command belongs to.

       Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration.

       To delete the cluster configuration, halt the cluster first.  To delete a package configuration you must halt the package first, but you do
       not need to halt the cluster (it may remain up or be brought down).  To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete
       all packages with STORAGE_GROUP defined.

       While  deleting	the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration.	In
       this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster.	If
       the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config-
       uration before doing any other Serviceguard command.

   Options
       cmdeleteconf supports the following options:

	      -f	Force the deletion of either the cluster configuration or the package configuration.

	      -v	Verbose output will be displayed.

	      -c cluster_name
			Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster.

	      -p package_name
			Name of an existing package to delete from the cluster.  The package must be halted already.   There  should  not  be  any
			packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only).

RETURN VALUE

       Upon completion, cmdeleteconf returns one of the following values:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       The high availability environment contains the cluster, clusterA , and a package, pkg1.

       To delete package pkg1 in clusterA, do the following:

	      cmdeleteconf -f -c clusterA -p pkg1

       To delete the cluster clusterA and all its packages, do the following:

	      cmdeleteconf -f -c clusterA

AUTHOR

       cmdeleteconf was developed by HP.

SEE ALSO

       cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m).

						      Requires Optional Serviceguard Software					  cmdeleteconf(1m)

Linux