Sponsored Content
Operating Systems AIX AIX Cluster Show shared file systems. Post 302923989 by Clovis_Sangrail on Wednesday 5th of November 2014 02:46:30 PM
Old 11-05-2014
Thanks very much, ibmtech.

When I try out the lspv command on the active and inactive nodes of the cluster, I see:

Code:
lihbidbp12pf:/home/lc25487 $ lspv
hdisk0          0005493a0a9eb0e2                    rootvg          active      
hdisk1          0005493a0a9eb1dd                    vg_scratch      active      
hdisk2          0005493a0a9eb3c4                    vg_fs1          active      
hdisk3          0005493a0a9eb4bf                    vg_fs2          active      
hdisk4          0005493a0a9eb6ab                    vg_fs3          active      
hdisk5          0005493a0a9eb7a6                    vg_fs4          active      
hdisk6          0005493a0a9eb98d                    vg_fs5          active      
lihbidbp12pf:/home/lc25487 $

on the actove node and I see:

Code:
lc25487@lihbidbp11pf: $ lspv
hdisk0          0005493a0a9eaef8                    rootvg          active      
hdisk1          0005493a0a9eb1dd                    vg_scratch                  
hdisk2          0005493a0a9eb3c4                    vg_fs1                      
hdisk3          0005493a0a9eb4bf                    vg_fs2                      
hdisk4          0005493a0a9eb6ab                    vg_fs3                      
hdisk5          0005493a0a9eb7a6                    vg_fs4                      
hdisk6          0005493a0a9eb98d                    vg_fs5                      
/home/lc25487

on the inactive node. I guess this means I do not have any concurrent filesystems, and that hdisk1-hdisk6 (with the same value in the 2nd field on each line) are attached to whichever node is active. The '-l' option on hdisk1 gives me:

Code:
lihbidbp12pf:/home/lc25487 $ lspv -l hdisk1
hdisk1:
LV NAME               LPs     PPs     DISTRIBUTION          MOUNT POINT
lv_3500               16      16      00..16..00..00..00    /3500
home_lv               48      48      00..48..00..00..00    /3500/home
lv_sca                96      96      96..00..00..00..00    /SCA
scr_lv                96      96      00..45..51..00..00    /3500/scratch
lv_orsyp              96      96      00..00..57..39..00    /3500/orsyp
download_lv           96      96      00..00..00..70..26    /3500/download
lihbidbp12pf:/home/lc25487 $

So I guess these are all logical volumes within hdisk1.

Again, thanks for the info.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

remote file copy across 2 systems (AIX and SCO)

Hello, Pls i need to copy some data from AIX Unix 4.3 to a SCO Openserve 5.0.5 using rcp command. But i keep on having permission error. WHAT IS THE SOLTION OR WHAT COMMAND CAN I USE AGAIN (4 Replies)
Discussion started by: aji
4 Replies

2. AIX

How to debug a shared library(.so file) on AIX?

How to debug a shared library(.so file) on AIX? (1 Reply)
Discussion started by: AlbertGao
1 Replies

3. AIX

IBM AIX on AS/400 Systems

Sry for my beginner question. I didn't find a list with all supported server types for an AIX 5.3 installation. Unfortunately ibm.com page has problems with the sign in so I can't ask in the ibm foum. Will AIX 5.3 run on a 9402, 9404 or 9406 system? Thanks for your help. (3 Replies)
Discussion started by: analyzer
3 Replies

4. UNIX for Dummies Questions & Answers

Printing systems in Solaris, AIX and HP-UX

Hi, Can anybody teach me the printing systems supported for Solaris 9, AIX and HP-UX 11i. Thanks in advance.:) (0 Replies)
Discussion started by: meeraramanathan
0 Replies

5. AIX

Breaking AIX cluster

Hello All, I was just wondering: How do I break a server cluster in an AIX 5.2 environment? Thanks. (1 Reply)
Discussion started by: bbbngowc
1 Replies

6. AIX

changing values for nfs shared file system on aix

Hi, I want to change the values for shared file system in aix for that I have run the command smitty chnfsexp but I am not getting the all the values which I have seen while adding the file system while exporting example smitty chnfsexp but after selecting shared file system using F4... (3 Replies)
Discussion started by: manoj.solaris
3 Replies

7. AIX

Should I be worried about my AIX Cluster?

I have a 2-node Power 7 - 16cpu - 32gb RAM - AIX 6L cluster. The production node has 10 physical cpus (40 cores) and 24gb of RAM. The cluster has been live for 6 weeks and I'm seeing some things on the production node that I think could be of concern but wanted to get some opinions. The... (6 Replies)
Discussion started by: troym72
6 Replies

8. AIX

AIX 5.2 C++ shared object issue

Hi all, I am developing an application with two components. One "c" binary and one "C++" shared object. While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly. I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies

9. AIX

AIX flag to reduce size of shared file

I am using xlC (Version: 11.01.0000.0011). While build i am using "-g" to have debug information in build. there are many object files (>500) due to which resultant shared file (.so) will have huge size. I can't reduce optimization level. Is there any way or flag is present by using which i... (2 Replies)
Discussion started by: Abhi04
2 Replies
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)
All times are GMT -4. The time now is 04:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy