03-12-2012
Exactly
Quote:
Originally Posted by
enzote
The disk are in concurrent mode. If a run lspv from one node I got:
# lspv
...
hdisk3 00f6317b414624c2 vg_data concurrent
hdisk4 00f6317b41466700 vg_data concurrent
...
I tried export/import.
The disks are mapped through VSCSI.
I will make a test, unmapping the disks, running cfgdev on VIOS and then remapping them.
Thanks!
Enzote
---------- Post updated at 09:41 AM ---------- Previous update was at 08:12 AM ----------
Hello!
This procedure works:
1.- Stop PowerHA services in both nodes.
2.- In VIOS A:
$ rmdev -dev vtd_data_A
$ rmdev -dev vtd_data_B
$ r oem
# rmdev -dl hdisk1
# rmdev -dl hdisk2
# cfgmgr
# chdev -l hdisk1 -a reserve_policy=no_reserve
# chdev -l hdisk2 -a reserve_policy=no_reserve
# exit
$ mkvdev -vdev hdisk1 -vadaper vhost0 -dev vtd_data_A
$ mkvdev -vdev hdisk2 -vadaper vhost0 -dev vtd_data_B
3.- Repeat step 2 en VIOS B.
4.- On node A:
# rmdev -dl hdisk3
# rmdev -dl hdisk4
# cfgmgr
# chdev -l hdisk3 -a reserve_policy=no_reserve
# chdev -l hdisk4 -a reserve_policy=no_reserve
# chdev -l hdisk3 -a queue_depth=10
# chdev -l hdisk4 -a queue_depth=10
# varyonvg vg_data
0516-1434 varyonvg: Following physical volumes appear to be grown in size.
Run chvg command to activate the new space.
hdisk3 hdisk4
# chvg -g vg_data
# varyoffvg vg_data
5.- Repeat step 4 on node B, except chvg -g.
Thanks for the support!
Enzote
This is why I asked if they were mapped as VSCSI as the new disks needed re-mapping.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi All,
one of the mount point in Hp ux server has reached 95%
its a data base file and can not be deleted.
so i want to know how to increase the size of mount point
i am new to unix ,please help me (1 Reply)
Discussion started by: jyoti
1 Replies
2. AIX
Hi
i increased the lv size using smit hacmp.
but, the new size is not reflecting.. why?.
the pp size is 512 MB. before it was 4 PP's. i increased to 10 PP's.
when i type df -m /xxx.. it is showing 2GB only.
see the info below..
root@db:/ > df -m /xxx/xxx
Filesystem MB blocks Free... (2 Replies)
Discussion started by: honeym210
2 Replies
3. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
4. UNIX for Dummies Questions & Answers
Unix protect its password by using salt
It that mean larger the salt size the more secure?
if the salt size increase greatly, will the password still able to be cracked?
thank you for helping (1 Reply)
Discussion started by: cryogen
1 Replies
5. Solaris
What is the largest possible LUN size that can be presented to Solaris 10. I've been googling a lot about this. The new EFI lablels (an alternative to VTOC) supports LUNs greater than 2TB. I need to know the upper limit. please help me find it. (4 Replies)
Discussion started by: pingmeback
4 Replies
6. AIX
How to increase the filesystem size in HACMP.
what is the difference between normal chfs command and increase the filesystem size in HACMP. (4 Replies)
Discussion started by: AIXlearner
4 Replies
7. UNIX for Dummies Questions & Answers
hi guys
I am working on my vmware workstation.
I have a /dev/sdb which is 5GB. I am using LVM.
Now I increase /dev/sdb 2 more GB.
fdisk -l shows 7 GB but pvscan still shows 5GB.
how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and... (1 Reply)
Discussion started by: kopper
1 Replies
8. AIX
Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server )
Is it possible to create HACMP cluster between two VIOS servers
Physical Machine_1
VIOS_SERVER_1
LPAR_1
SHARED_DISK_XX
VIOS_SERVER_2
Physical Machine_2
LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies
9. AIX
Hi,
Is there any advantage is making all my storage LUNS ( hdisk ) of uniform size. Currently the LUN's are having different size () eg: 50G / 60G / 75G etc ).
I am planning for a storage migration....so should i go for uniform lun size or with current LUN size pattern ?
Regards,
jibu (3 Replies)
Discussion started by: jibujacob
3 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
LEARN ABOUT HPUX
vxdiskadd
vxdiskadd(1M) vxdiskadd(1M)
NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager
SYNOPSIS
vxdiskadd disk_address_pattern_list
DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd
prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned
replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for
the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the
disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or
allows the user to ask to make the decision for each disk individually.
One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of
this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to
specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case
of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the
specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify
all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more
examples:
all: all disks
c3 c4t2: all disks on controller 3 and controller 4, target 2
c3t4d2: a single disk (in the c#t#d# naming scheme)
xyz_0 : a single disk (in the enclosure based naming scheme)
xyz_ : all disks on the enclosure whose name is xyz
The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by
vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec-
ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0.
All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate.
Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message.
OPERATIONS
Reconnecting a drive that was temporarily inaccessible
This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the vxrecover utility.
Initialization of a disk with reserved regions
Initialization of the disk is performed by calling vxdisksetup.
Adding a disk to an existing disk group
This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so
that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free
space.
Creation of new disk groups in which to import a new disk
If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is
offered.
Hardware-Specific Note
Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM
follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the
force option. The force option ignores any such storage-specific guidelines.
FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations.
/etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations.
/etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations.
NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted
as CDS disks.
SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)