05-22-2009
You can find 'CSPOC' option in "smitty hacmp".
Through this you can increase the filesystem, and this will take care of updating ODM entries and timestamp of the filesystem in all the nodes of the cluster.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
my file system size /hd4 is keep on increasing continuously , i tried all the performance related command to identify which process is currently running........
for every minute my FS(/hd4) size is increasing ?what could be the problem?
how to diagnose it ?
is there any specific command... (3 Replies)
Discussion started by: aixteam
3 Replies
2. Solaris
Hi all,
aloe:root-> df �k
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/vx/dsk/rootvol 8254263 2064133 6107588 26% /
/proc 0 0 0 0% /proc
mnttab ... (2 Replies)
Discussion started by: krishna176
2 Replies
3. Solaris
Hi All,
I need to increase the filesystem of / and /var (two different slices)? Space will be coming from /home slice so I need to decrease it. Is that possible without reinstallation or in a single-user-mode?
Any idea or link please.
Thanks in advance. (5 Replies)
Discussion started by: itik
5 Replies
4. UNIX for Dummies Questions & Answers
Hi..
I want to increase the file system size of any filesystem online, without using the Volume manager like LVMs, is it possible? & if yes then how? (3 Replies)
Discussion started by: Amol21
3 Replies
5. AIX
Hello,
Does HACMP have bugs ? I have version 5.4 on AIX 6.1 and when I try to increase filesystem space or logical volume partitions which are under HACMP VG it gives me error:
# lsvg
rootvg
pr0oravg
px0oravg
pb0oravg
pr0sapvg
px0sapvg
pb0sapvg
pr1_pr2_vg
pr2_px1_vg
#
#... (11 Replies)
Discussion started by: filosophizer
11 Replies
6. AIX
There is a shared volume group connected to two AIX systems A and B on a shared storage. The shared volume group was regularly attached to the system A and in case of a system A crash, the system B should take over the shared volume group and resources on it. Resources on the shared storage:... (1 Reply)
Discussion started by: yamanu
1 Replies
7. AIX
Hello!
I have this infraestructure:
- 1 POWER7 with single VIOS on Site A.
- 1 POWER6 with single VIOS on Site B.
- 1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
- 1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
- 1 Storage DS4700 on Site A.
- 1... (8 Replies)
Discussion started by: enzote
8 Replies
8. UNIX for Advanced & Expert Users
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
9. Red Hat
Hi
I am using oracle linux 6.4. My hard drive capacity is 500 GB. my filesystem size onbly 50GB. I would like to extend my filesystem size to around 100GB. I tried many codes but still I am not able.
this is the output of df -h :
Filesystem Size Used Avail Use% Mounted on... (6 Replies)
Discussion started by: farshad
6 Replies
10. AIX
I an trying to increase the file size on an AIX 5.3 box. I think i am missing the correct syntax for the command. Here is was i am trying on a test box
# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0000bd8b00004c00000
0010d8ed7a76e
VG STATE: active ... (3 Replies)
Discussion started by: fierfek
3 Replies
cmruncl(1m) cmruncl(1m)
NAME
cmruncl - run a high availability cluster
SYNOPSIS
cmruncl [-f] [-v] [-n node_name...] [-t | -w none]
DESCRIPTION
cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster.
To start a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration
file. See access policy in cmquerycl(1m).
This command should only be run when the cluster is not active on any of the configured nodes. This command verifies the network configu-
ration before causing the nodes to start their cluster daemons. If a cluster is already running on a subset of the nodes, the cmrunnode
command should be used to start the remaining nodes and force them to join the existing cluster.
If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster. All nodes in the cluster must be
available for the cluster to start unless a subset of nodes is specified.
Options
cmruncl supports the following options:
-f Force cluster startup without warning message and continuation prompt that are printed with the -n option.
-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 packages.
The -w option is not required with the -t option as -t does not validate network connectivity, but assumes that all the
nodes can meet any external dependencies such as EMS resources, package subnets, and storage.
-n node_name...
Start the cluster daemon on the specified subset of node(s).
-w none By default network probing is performed to check that the network connectivity is the same as when the cluster was config-
ured. Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The
option should only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmruncl returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon:
cmruncl
Run the cluster daemons on node1 and node2:
cmruncl -n node1 -n node2
AUTHOR
cmruncl was developed by HP.
SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmruncl(1m)