How To List Volume Groups and Their Characteristics

April 18th, 2009

I introduced Volume Groups in one of my previous posts. In this post I’m going to discuss, how to carry out common operations on Volume Groups. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction.

Here are few things which I’m gonna discuss in this post:

How To List Volume Groups
Using command lsvg provides the complete list of Volume Groups available in the system. That does not matter whether the volume group is varied on or varied off.
e.g.
wiw_labs:$ lsvg
altinst_rootvg
rootvg
myvg
appvg

How To List Only Varied On Volume Groups
Using command lsvg, with -o option provides the list of Volume Groups which are currently varied on. Varied on means the Volume Group is open for use.
e.g.
wiw_labs:$ lsvg -o
rootvg
appvg

How To List Volume Group Characteristics
To list characteristics of a particular Volume Group, we use the lsvg command with -l option and name of Volume Group.

e.g wiw_labs:$ lsvg appvg

VOLUME GROUP appvg VG IDENTIFIER 005ab34300004c00000000ff753cd62b
VG STATE active PP SIZE 64 megabyte(s)
VG PERMISSION read/write TOTAL PPs 1618 (103552 megabytes)
MAX LVs 256 FREE PPs 215 (13760 megabytes)
LVs 25 USED PPs 1403 (89792 megabytes)
OPEN LVs 25 QUORUM 1 (Disabled)
TOTAL PVs 2 VG DESCRIPTORS 3
STALE PVs 0 STALE PPs 0
ACTIVE PVs 2 AUTO ON yes
MAX PPs per VG 32512 Â Â
MAX PPs per PV 2032 MAX PVs 16
LTG size 128 kilobyte(s) AUTO SYNC no
HOT SPARE no BB POLICY relocatable

Below is explained the meaning of various terms used in the listing:

  1. Volume Group: Name of Volume Group.
  2. VG State: active/partial. Partial indicates that some of the Physical Volumes in the Volume Group are not active. See this for more on VG state.
  3. VG Permission: It indicates if the volume group is read-only or read-write.
  4. Max LVs: Maximum number of Logical Volumes allowed in Volume Group.
  5. LVs: Total number of Logical Volumes at present in Volume Group.
  6. Open LVs: Number of LVs open at present in the Volume Group for any Read Write operation.
  7. Total PVs: Total number of Physical Volumes present in Volume Group.
  8. Stale PVs: How many stale Physical Volumes are there in Volume Group. The stale Physical Volumes are those ones on which I/O operations are not possible.
  9. Active PVs: Total number of Physical Volumes which are active in Volume Group.
  10. Max PPs per VG: Maximum no. of Physical Partitions which can be there in the Volume Group.
  11. Max PPs per PV: Maximum number of Physical Partitions which can be there in Physical Volume.
  12. VG Identifier: The very long string to identify Volume Group.
  13. PP Size: The size of Physical Partition used in every Physical Volume of Volume Group.
  14. Total PPs: Total number of Physical Partitions in Volume Group.
  15. Free PPs: Total number of free Physical Partitions with in Volume Group.
  16. Used PPs: Total number of Physical Partitions in use in Volume Group.
  17. Quorum: Whether the quorum is on or not in Volume Group.
  18. VG Descriptors: Number of Volume Group Descriptor Areas(VGDA) in Volume Group.
  19. Stale PPs: How many Physical Partitions are stale or unable to perform I/O operations.
  20. Auto On: Whether the Volume Group will varyon on system startup or not.
  21. Max PVs: Maximum number of Physical Volumes allowed in this Volume Group.
  22. Auto Sync: Whether this Volume Group should sync automatically or not.
  23. BB Policy: Its bad block relocation policy. So, this value here is relocatable, that means we are allowed to relocate bad blocks in this Volume Group if need be.

(Refer AIX Manpages for more details.)

Share

Posted in LVM | No Comments »

Comments

Leave a Reply

 Comment Form 

 


More articles from the category: LVM


The mkvg FAQs

Here in this post I’m presenting few things in the form of FAQs. The can be used as a ready reference while creating Volume Groups. To know how to create Volume Group read the article: How To Create Volume Group.

Share

How To Create Volume Group

Lots of things need to be considered while creating Volume Groups. In this post I’m presenting various scenarios of Volume Group creation. In the previous post I introduced you to listing of Volume Groups. For the ones interested in fundamentals of Logical Volume Manager read the previous article: Aix Logical Volume Manager A Brief Introduction…

Share

How To List Volume Groups and Their Characteristics

I introduced Volume Groups in one of my previous posts. In this post I’m going to discuss, how to carry out common operations on Volume Groups. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction.
Here are few things which I’m gonna discuss in this post:

Share

Reorganize Volume Group What Is It And How To Do It?

What is reorganization of a Volume Group and why its needed, is a bit confusing for the system administrators. Here in this article I am explaining it to make it easier for the reader

Share

How To Work With Physical Volumes

I’ve written in my previous posts about introduction to Physical Volumes. There I also discussed some operations to be carried out on Physical Volumes. Now, I’ll be discussing some other operations on Physical Volumes like listing Physical Volumes, Logical Volumes on Physical Volumes, Physical Partitions allocations etc. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction.

Share

File Systems In AIX-A Primer

Generally talking, the File Systems are collection of files, directories etc. within a single partition or Logical Volume in a Volume Group. Collecting files and directories from different Logical Volumes or Partitions does not qualify to be named as File System. Aix supports mainly three types of File Systems: JFS, NFS and CDRFS. All these are being discussed here in this article. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction

Share

Logical Volume In AIX A Primer

Users can not access directly, the disk space available on Physical Volumes with in Volume Group. In order to access the space available, the users and applications need to access File Systems which are created on Logical Volumes. Therefore to manage Physical Volume space you need to manage Logical Volumes. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction….

Share

Volume Group In AIX – A Primer

Volume Group is at the highest level in LVM hierarchy. Hard disks are used as Physical Volumes in LVM. Then Physical partitions are mapped to Logical Partitions. Logical Partitions are combined to Logical Volumes. These Logical Volumes comprise the Volume Group. For more information you can see the previous article: Aix Logical Volume Manager A Brief Introduction..

Share

How Does AIX Deal With Bad Blocks

The biggest concern for any organization using a server is data integrity. The various solutions like Network Attached Storage, Storage Area Networks, high availability servers, online data backup and disaster recovery solutions are among the available solutions.

Share

AIX Logical Volume Manager A Brief Introduction

The storage in Aix can be divided in two layers: Physical and Logical.

On physical level the two things come into picture:

1. Physical Volume(PV).
2. Physical Partition(PP).

On logical level the storage is divided in three parts:

1. Logical Partition(LP).
2. Logical Volume(LV).
3. Volume Group(VG).

Share

Physical Volume In AIX – A Primer

Physical Volume in AIX is a hard drive with special characteristics which are useful for LVM(Logical Volume Control). So, if any hard drive is to be used for LVM purpose, it needs to be made as Physical Volume. Physical Volume has several properties which differentiate it from normal hard drive. These are listed as below…

Share

Non Concurrent, Concurrent and Enhanced Concurrent Volume Groups

Often the confusion arises among these types. I am trying to clarify the differences.The terms often apply in clustering scenario.

Non Concurrent VG
In Non Concurrent VG, application runs typically on a single node only and data of VG is accessible to that node only. If however present…

Share

Quorum-What it is and Why is it Needed

The importance of Quorum concept lies in fact that if quorum is enabled and VGDAs fall below 51% then the data on VG may be corrupted if VG remains varied on. Thats why quorum enabled VG is varied off if quorum falls below 51%. This way data is safe on VG because disk

Share