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
scconf_quorum_dev_scsi(1M)				  System Administration Commands				scconf_quorum_dev_scsi(1M)

NAME
scconf_quorum_dev_scsi - Add and remove shared SCSI quorum devices and change various SCSI cluster quorum configuration properties or states. SYNOPSIS
scconf {-a|-c|-r} -q globaldev=devicename otheroptions scconf {-a|-c|-r} -q name=devicename otheroptions DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. A SCSI quorum device is considered to be any Sun Cluster supported, attached storage that is connected to two or more nodes of the cluster. The device must be managed by DID, and the device name that is provided must be a DID device name. The SCSI quorum device has no other properties that can be specified. OPTIONS
The following options are specific to shared disk quorum devices. See scconf(1M) for the list of supported generic options. See scconf_quo- rum_dev_netapp_nas(1M) for options that are specific to NAS quorum devices. The add and remove forms of the command are used to add and remove shared quorum devices to or from the configuration. The change form of the command is used for changing various properties of cluster quorum configuration. The -q quorum-options available for each of the three forms of the command can be used to change the cluster quorum configuration are as follows: Add a shared quorum device: -q -a globaldev=devicename[, node=node,node=node[, ...]] or -q -a name= devicename,type=scsi or -q -a autoconfig[,noop] Change a property or state of quorum configuration: -q -c globaldev=devicename,{maintstate | reset} or -q -c autoconfig[,noop] Remove a shared quorum device: -q -r globaldev=devicename or -q -r name=devicename autoconfig When used with the add form of the command, automatically chooses and assigns one quorum device in the two-node cluster. The quorum device is chosen from the available devices. If a quorum device is already configured, the command aborts. When used with the change form of the command, automatically chooses and assigns one device that replaces all existing quorum devices in the two-node cluster. The quorum device is chosen from the available devices. All available devices in the cluster must be qualified to be a quorum device. The autoconfig suboption does not assess whether an available device is qualified to be a quorum device. If the cluster contains more than two nodes, the autoconfig suboption makes no changes to the quorum configuration. Do not use the autoconfig suboption if you intend to configure a NAS device as quorum. [,noop] Is valid with the autoconfig suboption. The command prints to standard output the list of quorum devices that the autoconfig suboption would add or change. The autoconfig,noop suboption makes no changes to the quorum configuration. When scconf is interrupted or fails while performing quorum-related operations, quorum configuration information can become inconsistent in the cluster configuration database. If an inconsistency occurs, either run the same scconf command again or run it with the reset option to reset the quorum information. With the add form of the command, if a name is specified without a node list, the quorum device is added with a port defined for every node to which the device is attached. But, if a node list is given, at least two nodes must be provided, and each node in the list must be ported to the device. EXAMPLES
Example 1 Adding SCSI Quorum Devices The following scconf commands adds a SCSI quorum device. -a -q globaldev=/dev/did/rdsk/d4s2 or -a -q name=/dev/did/rdsk/d4s2,type=scsi Example 2 Changing SCSI Quorum Devices The following scconf command changes a SCSI quorum device configuration. -c -q globaldev=/dev/did/rdsk/d4s2,reset or -c -q name=/dev/did/rdsk/d4s2,reset Example 3 Removing SCSI Quorum Devices The following scconf command removes the SCSI quorum device. qd1. -r -q globaldev=qd1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scconf_quorum_dev_netapp_nas(1M) Sun Cluster 3.2 10 Apr 2006 scconf_quorum_dev_scsi(1M)
All times are GMT -4. The time now is 06:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy