03-07-2013
Quote:
Originally Posted by
MichaelFelt
yes, you can if the stoarge is an hdisk to the vios, not when the storage is a file or logical volume.
if i recall, just repeat the mkvdev command.
So, I can assign same HDISK to two or more , LPARs
example: from SAN Storage I have allocated HDISK8 to PowerVM IVM
I will have to create virtual scsi for all three LPARs
then assign HDISK8 to them, and as you mentioned above would have to set the reserve_policy=no_reserve .
is this right ?
10 More Discussions You Might Find Interesting
1. AIX
Hello,
I would like to know if anyone has faced this problem. Whenever there is a duplicate IP address, HACMP goes down infact HACMP ( PowerHA ) takes the whole system down.
Does anyone know how to solve this problem ? (3 Replies)
Discussion started by: filosophizer
3 Replies
2. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
3. AIX
I am planning for building a new database server using AIX 6.1 and Oracle 11.2 using ASM.
As i have learned starting with Oracle 11.2 ASM can only be used in conjunction with Clusterware, which is Oracles HA-software. As is the companies policy we do intend to use PowerHA as HA-solution instead... (1 Reply)
Discussion started by: bakunin
1 Replies
4. 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
5. AIX
Hello AIX GURU's
Can anybody tell me the steps to crate shared VG (enhanced concurent) for my Lpars from VIO server?
my questions are:
1.
Should I crate Enhanced Concurent VG in VIO and map it using virtual Scsi to Lpar?
or
2. Can I just create virtual SCSI in VIO and map to Lpar and... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
6. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
7. AIX
Hello,
AIX 6.1 TL7 SP6
POwerHA 6.1 SP10
I was experimenting with new hacmp build. It's 3-node cluster build on AIX 6.1 lpars. It contains Ethernet and diskhb networks. Shared vg disk is SAN disk. Two nodes see disk using vscsi, third node sees disk using npiv. Application is db2 server.
... (4 Replies)
Discussion started by: vilius
4 Replies
8. AIX
hello
ive installed powerha 7.1.3 on two servers aix 6.1.9 6100-09-03-1415
work with dmx4 EMC storgae.
after sync cluster ( terminate with OK ) ive see that the repository disk upper only in one machine :
hdiskpower60 00c7f6b59fc60d9d caavg_private active... (1 Reply)
Discussion started by: ariec
1 Replies
9. AIX
I have created a VxVM disk group in AIX7.1. I have tried to added this VxVM disk group in powerHA 6.1. But in cluster VxVM DGs are not listing. Is there any other procedure to add vxvm diskgroup to hacmp.
Please share me steps for adding vxvm diskgroup to hacmp. (6 Replies)
Discussion started by: sunnybee
6 Replies
10. AIX
Hi All,
As per the IBM upgrade/support matrix
IBM Techdocs Technote: PowerHA for AIX Version Compatibility Matrix
we can't do online upgrade or rolling migration from powerha v7.1.0 to v7.1.3. on AIX61_TL9_SP4, So we are following the steps as below ...
1 ) Bring down the cluster
2 )... (2 Replies)
Discussion started by: linux.amrit
2 Replies
fsapadm(1M) fsapadm(1M)
NAME
fsapadm - VxFS allocation policy administration utility
SYNOPSIS
metadata_policy_name
flags] filename data_policy_name metadata_policy_name
flags] order] mount_point policy_name volname...
DESCRIPTION
The utility performs administrative tasks, such as assigning, defining, deleting, and enforcing allocation policies in a specified VERITAS
File System.
policy_name specifies the name of an allocation policy. The maximum length of an allocation policy name is 64 characters.
mount_point specifies the directory on which the file system is mounted.
Keywords
Assigns allocation policies to a Storage Checkpoint.
Assigns allocation policies to an individual file.
Possible values for flags are:
Set this flag on a directory and subsequently the files created in the directory will inherit the allocation policies.
Assigns the default allocation policies for an entire file system.
Defines a new allocation policy
or changes an existing allocation policy named policy_name at the specified mount point. In the latter case, the previously
specified volumes are replaced by the newly specified volumes.
Possible values for order are:
Allocations are done from the volume in the order in which they are given in the allocation policy.
Allocations are done from the volume specified in the allocation policy
that has the most free blocks.
Allocations are done from a volume that is selected in a round-robin
fashion from those specified in the allocation policy.
The default order is
Possible values for flags are:
Allows non-privileged users to be able to assign the policy using the keyword. By default, only privileged users can assign
policies.
Deletes an allocation policy.
Enforces the allocation policies assigned to an individual file by
moving any data and metadata that does not fulfill its assigned allocation policy into new blocks that do fulfill its
assigned allocation policy.
Displays the definitions of all allocation policies
defined in a file system.
Displays the definition of an allocation policy.
Displays the allocation policies assigned to an entire file system.
Displays the allocation policies assigned to a Storage Checkpoint.
Displays the allocation policies assigned to an individual file.
EXAMPLES
The following command defines an allocation policy named using volumes and with order in the file system mounted at
The following command deletes the allocation policy named from the file system mounted at
The following command displays the definition of the allocation policy named in the file system mounted at
The following command assigns the allocation policies named and as the default policies for data and metadata, respectively, for all files
in the file system mounted at
The following command assigns the allocation policy named as the default policy for data and metadata, respectively, for the Storage Check-
point in the file system mounted at
The following command assigns the allocation policy named for data and metadata, respectively, to the file
The following command displays the allocation policies assigned as the defaults for all files in the file system mounted at
The following command displays the allocation policies assigned to the Storage Checkpoint in the file system mounted at
The following command displays the allocation policies assigned to the file in the file system mounted at
The following command enforces the allocation policies assigned to the file in the file system mounted at (that is, the existing alloca-
tions are moved to match the policies, if required):
SEE ALSO
fsadm_vxfs(1M), fsckptadm(1M), fsvoladm(1M).
fsapadm(1M)