Sponsored Content
Full Discussion: Lspv -free command on VIOS
Operating Systems AIX Lspv -free command on VIOS Post 302870307 by m_raheelahmed on Saturday 2nd of November 2013 03:52:11 AM
Old 11-02-2013
Lspv -free command on VIOS

Hi all,

When we run lpsv -free command on VIOS, it will take lot of time to display free disks i.e around 8 to 10 minutes. VIOS ioslevel is 2.2.1.4Can you have any solution for this problem?

Many Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to Use the Free Command in Linux

I know that free command displays memory usages however I like to know how the option and the results when I use this command.. PLease respond ASAP thanx... I am a newbie.. :D (1 Reply)
Discussion started by: LiTo
1 Replies

2. UNIX for Advanced & Expert Users

AIX p570 lspv, lslv etc... not working

Hi we are running a VIO server on a AIX p570 we cannot run and of the command the query the ODM has anyone seen this problem or has a solution the command just hangs. (1 Reply)
Discussion started by: truma1
1 Replies

3. Shell Programming and Scripting

Awk command for search a string in lspv

I want to know wich hdisk have only one pvid and also display hdisk with two pvid. hdisk1 00c3fcd4e516183f testvg active hdisk2 00c3fcd4e516189b testvg active hdisk3 00c3fcd4e51618ec testvg ... (1 Reply)
Discussion started by: khalidou13
1 Replies

4. Shell Programming and Scripting

Awk command for search a string in lspv

I 've got this retourn when i tape the commande lspv: hdisk0 00c3fce454950416 rootvg active hdisk1 00c3fce454950416 rootvg active I want to verify if hdisk0 et hdisk1 have the same pvid (ex : 00c3fce454950416)? Can... (8 Replies)
Discussion started by: khalidou13
8 Replies

5. UNIX for Dummies Questions & Answers

Doubt on free command

All, I have doubts related to free command in Linux. My environment is RHEL5 - 64 bit OS We have 2 node RAC database installed Query output from node 1 is Free -g Total used free shared buffers cached Mem: 32 25 7 0 5 15 -/+ buffers/cache: 4 27 Swap: 30 0 30 Query... (2 Replies)
Discussion started by: user7509
2 Replies

6. UNIX for Advanced & Expert Users

Output of Free command in unix?

Hello, I need some help to interpret the below output... What is -/+ buffers/cache? My understanding is, total RAM is 3986152 Bytes, used RAM is 3950904 bytes. What is buffers and cached?? Can any one please interpret this output? It would be great help if some one can help me on this? ... (2 Replies)
Discussion started by: govindts
2 Replies

7. AIX

VIOS IP address - separate vlan for vios servers ?

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

8. Red Hat

Need help on top and free command.

Hi, from below output.How to read or relate one marked in bold. $ free -m total used free shared buffers cached Mem: 129176 92753 36423 0 2268 39973 -/+ buffers/cache: 50511 78664 Swap: 31996 ... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

9. AIX

Lspv -free command on VIOS

Hi all, We have observed that lspv -free command tooks 15 to 20 minutes to display the free disks and we have only 77 MPIO disks on VIO Server. Our VIOS version is 2.2.1.4. Please let us know what could be the reason that lspv -free command taking long time to display the output. Thank (4 Replies)
Discussion started by: m_raheelahmed
4 Replies

10. AIX

Different sizes with getconf DISK_SIZE and lspv

Hi all, when I issue a lspv <hdisk>, I get TOTAL PPs: 7199 (1842944 megabytes) When I issue a getconf DISK_SIZE /dev/<hdisk>, I get 1048576 Where do those additional ~800 GB come from the output of lspv.. anyone an idea? The volume is an EMC LUN provided by a VIOS and... (2 Replies)
Discussion started by: zaxxon
2 Replies
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)
All times are GMT -4. The time now is 10:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy