Sponsored Content
Operating Systems AIX New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config? Post 302932956 by c3rb3rus on Monday 26th of January 2015 05:04:42 PM
Old 01-26-2015
Thanks this helps Smilie I will make sure the microcode/firmware is up to the latest available before I move this into production.

This is a standalone box, so no LPM.

---------- Post updated at 02:04 PM ---------- Previous update was at 01:36 PM ----------

Hey bakunin,

Here is a question for you on pv/vg in regards to my new system setup...

I have carved a 350GB LUN from my StorWize SAN and presented it to the Power8 box via FC.

The pv hdisk2 has the following attributes (the hdisk2 is the LUN I carved and presented)..

Code:
# lspv hdisk2
PHYSICAL VOLUME:    hdisk2                   VOLUME GROUP:     vg_usr2
PV IDENTIFIER:      00f9af9427d70816 VG IDENTIFIER     00f9af9400004c000000014b28233d7d
PV STATE:           active
STALE PARTITIONS:   0                        ALLOCATABLE:      yes
PP SIZE:            512 megabyte(s)          LOGICAL VOLUMES:  1
TOTAL PPs:          699 (357888 megabytes)   VG DESCRIPTORS:   2
FREE PPs:           0 (0 megabytes)          HOT SPARE:        no
USED PPs:           699 (357888 megabytes)   MAX REQUEST:      256 kilobytes
FREE DISTRIBUTION:  00..00..00..00..00
USED DISTRIBUTION:  140..140..139..140..140
MIRROR POOL:        None

After some googling I understand that a normal VG is limited to 32512 physical partitions (32 physical volumes each with 1016 partitions) and 256 logical volumes.

Now I am already confused, hope you can demystify some stuff..

My "hdisk2" has 699 total physical partitions (Total PPs?) based on PP Size being 512mb chunks. So this is 699 out of 32,512 or 1016?

If I changed the hdisk2 to have a PP Size of 256mb chunks, the Total PPs would be 1398 correct? Is there any performance benefits of making the PP Size smaller vs. larger? I am trying to decide what I want my PP Size to be for the PVs.

In the end I will have 4 enhanced JFS2 FS each allocated 350GB, 1TB, 1T, and 2.45TB.

Moderator's Comments:
Mod Comment edit by bakunin: changed the QUOTE- to CODE-tags, the output is easier to read that way.

Last edited by bakunin; 01-26-2015 at 06:14 PM..
 

10 More Discussions You Might Find Interesting

1. AIX

ibm san cache battery with aix

Hi All, I would like to share this incident that happened the other day. I have a question with this, https://www.unix.com/aix/64921-create-new-vg-san-rename-fs.html And I thought it's related to the above link but the problem was the ibm san 4300 cache battery was dead and I need to click... (2 Replies)
Discussion started by: itik
2 Replies

2. Filesystems, Disks and Memory

First steps on Ibm SAN DS4500

Hello everyone ! Im new on Ibm San DS4500. Can you give me some tips to this, because I dont want to make a mistake. I have some questions. How can I know how much space get on the san, I cant find it. How can add more space to a partition. Do you have some tutorial about this. I... (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

3. AIX

Question about IBM San Ds4500

I have a question about SAN commands I have almost 15Tb of disk on my san but assigned and something else I have almost 11Tb There is a command to know, what its my real total storage capacity and another command to know how much I used .? Thanks again in advance (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

4. AIX

Which Forum for IBM Storage production are good?

Which Forum for IBM Storage production are good? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

5. Solaris

Cannot see the IBM SAN storage

HI all, I had recently change the Server storage from EMC to the IBM SAN. but after the configuration, the IBM success to see the server HBA port and successfully assign a LUN for the server. When i go to the server, and restarted it. i use the "format" command to check, but din see any... (1 Reply)
Discussion started by: SmartAntz
1 Replies

6. AIX

IBM SAN storage -- cache battery

Hello, I have IBM SAN STORAGE DS4100 and one of the cache battery for the controller is dead. Suddenly the performance has been degraded and access to SAN disks ( reading and writing ) became very slow ? My query: Replacing the battery will take 6 days, so in the mean time what are the ways... (1 Reply)
Discussion started by: filosophizer
1 Replies

7. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies

8. AIX

IBM AIX - SAN Storage DS4300 issue

Hi, This is follow up to the post https://www.unix.com/aix/233361-san-disk-appearing-double-aix.html When I connected Pseries Machine HBA Card ( Dual Port ) directly to the SAN Storage DS4300 , I was able to see Host Port Adapter WWN numbers , although I was getting this message... (2 Replies)
Discussion started by: filosophizer
2 Replies

9. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

10. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies
vgdisplay(1M)															     vgdisplay(1M)

NAME
vgdisplay - display information about LVM volume groups SYNOPSIS
[vg_name...] vg_vers | vg_name ...] Remarks If a combination of volume groups version 1.0 and 2.0 or higher arguments are supplied, the arguments may not be processed in the order they are listed on the command line. DESCRIPTION
The command displays information about volume groups. For each vg_name specified, displays information for that volume group only. If no vg_name is specified, displays names and corresponding information for all defined volume groups. If the volume group version is speci- fied, displays names and corresponding information for all volume groups belonging to the specified volume group version. The volume group must be activated (see vgchange(1M)) before it can be displayed. Options and Arguments recognizes the following options and arguments: vg_name The path name of the volume group, for example, Display volume group information for all volume groups corresponding to the volume group version vg_vers. Produce a compact listing of fields described in The output is a list of colon separated fields formatted as value...]. For each volume group, display additional information about logical volumes, physical volumes, and physical volume groups. Display Without -v Option If you omit the option, only the following information is displayed: The path name of the volume group. Current access mode and quiesce mode of the volume group. The access mode is either or If the volume group is quiesced, the quiesce mode is displayed on the same line. The quiesce mode is either or State of the volume group: always as after a command, since deactivated volume groups are not displayed. Maximum number of logical volumes allowed in the volume group. Current number of logical volumes in the volume group. Number of logical volumes currently open in the volume group. Maximum number of physical volumes allowed in the volume group. Current number of physical volumes in the volume group. Number of physical volumes that are currently active. Maximum number (limit) of physical extents that can be allocated from any of the physical volumes in the volume group. Number of Volume Group Descriptor Areas within the volume group. Size of each physical extent in Megabytes. Total number of physical extents within the volume group: the sum of the number of physical extents belonging to each available physical volume in the volume group. (This does not include physical extents belonging to stand-by spare physical volumes; presence of these is only possible if you are using mirrored disks -- see below). Number of physical extents currently allocated to logical volumes. Number of physical extents not allocated (not including physical extents belonging to stand-by spares). Total number of physical volume groups within the volume group. Total number of physical volumes that are designated as spares for this volume group. This will include both stand-by and active spares -- see below. Total number of spare physical volumes that are active in place of (containing all data from) a failed physical volume. Volume Group version. The maximum size of the volume group. The units for this display are determined by a suffix: (megabytes), (gigabytes), (terabytes), (petabytes). For example: 256 terabytes would be 256t. For version 1.0 volume groups, it may not be possible to achieve the VG Max Size as it may be limited by the size of each physical volume in the volume group. The maximum number of extents in the volume group (VG Max Size/PE size). For version 1.0 volume groups, it may not be possible to achieve the VG Max Extents as it may be limited by the size of each physical volume in the volume group. Display With -v Option If you specify the option, lists the following additional information for each logical volume, for each physical volume, and for each phys- ical volume group in the volume group: Information about logical volumes belonging to vg_name: The block device path name of a logical volume in the volume group. State of the logical volume: Logical volume available but contains physical extents that are not current. Logical volume available with no stale extents. Logical volume is not available for use. Size of the logical volume. Number of logical extents in the logical volume. Number of physical extents used by the logical volume. Number of physical volumes used by the logical volume. Information about physical volumes belonging to vg_name: The block device path name of a physical volume in the group. When an alternate link to a physical volume has been added, is dis- played next to the device path name. (See vgextend(1M) for definition.) State of the physical volume: ( spare physical volumes are only relevant if you have installed HP MirrorDisk/UX software): The physical volume is available and is not a spare physical volume. The physical volume is available. However, its data still resides on an active spare. The physical volume is available and is an active spare physical volume. (An active spare is a spare that has taken over for a failed physical volume.) The physical volume is a spare "standing by" in case of a failure on any other physical volume in this volume group. It can only be used to capture data from a failed physical volume. The physical volume is unavailable and is not a spare physical volume. The physical volume is unavailable. However, it's data now resides on an active spare, and its data is available if the active spare is available. The physical volume is unavailable and it's an active spare. Thus, the data on this physical volume is unavailable. The physical volume is a spare "standing by" that is not currently available to capture data from a failed physical volume. Total number of physical extents on the physical volume. Number of free physical extents on the physical volume. If the physical volume represents an active spare, this field will show the name of the failed physical volume whose data now resides on this spare. This information can be used to manually move the data back to the original physical volume once it has been repaired (see pvmove(1M)). If it cannot be determined which physical volume that the data came from, this field will instead display A missing PV would indicate that when the volume group was last activated or reactivated (see vgchange(1M)), the "failed" physical volume was not able to attach to the volume group. If the physical volume represents a failed physical volume, this field will show the name of the active spare physical volume that now contains the data that originally residing on this volume. This information can be used to manually move the data back to the original physical volume (see pvmove(1M)) once it has been repaired. For multiported devices accessed via multiple paths, this field indicates the autoswitch behavior for the physical volume (see pvchange(1M)). LVM will automatically switch from the path it is using whenever a better path to the physical volume is available. LVM will switch paths when a better path recovers (after it had failed earlier), or if the current path fails and another path is available. This is the default. LVM will automatically switch to using the best available path only when the path currently in use is unavailable. LVM will continue using a specific path for the physical volume as long as it works, regardless of whether another better path recovers from a failure. This specifies LVM's proactive polling behavior on alternate paths of a physical volume. LVM will periodically test alternate paths of a physical volume and help to identify faulty paths before user I/O is affected. This is the default. No periodic testing of alternate paths of a physical volume will be performed. Information about physical volume groups belonging to vg_name: Name of a physical volume group in the volume group. The block device path name of a physical volume in the physical volume group. Compact listing (-F Option) The option generates a compact and parsable listing of the command output in colon separated fields formatted as value...]. The option is designed to be used by scripts. The resulting command output may be split across multiple lines. The output may include new keys and/or values in the future. If a key is deprecated, its associated value is set to For the current version of the command, the lines format is: The format of Line 1 is as follows: For volume groups version 2.0 or higher two additional fields are added to the LINE 1 format after the vg_version field. vg_name=value:vg_write_access=value:vg_status=value:max_lv=value: cur_lv=value:open_lv=value:max_pv=value:cur_pv=value:act_pv=value: max_pe_per_pv=value:vgda=value:pe_size=value:total_pe=value: alloc_pe=value:free_pe=value:total_pvg=value:total_spare_pvs=value: total_spare_pvs_in_use=value:vg_version=value:vg_max_size=value: vg_max_extents=value: The format of Line 2 is as follows: cluster:server=value:client=value[:...] The format of Line 3 is as follows: lv_name=value:lv_status=value:lv_size=value:current_le=value: allocated_pe=value:used_pv=value The above line may be repeated with different values. The format of Line m is as follows: pv_name=value[,value]:pv_status=value:total_pe=value:free_pv=value: spared_from_pv=value:spared_to_pv=value:autoswitch=value: proactive_polling=value The above line may be repeated with different values. The format of Line n is as follows: pvg_name=value:pv_name=value[,value...] The above line may be repeated with different values. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Display information about all the volume groups within the system: Display all of the information about one volume group, including the characteristics and status of both the logical and physical extents of the volume group: Display information about all the volume groups within the system that are of version 2.0: SEE ALSO
lvdisplay(1M), lvmadm(1M), pvdisplay(1M), vgchange(1M), vgcreate(1M). vgdisplay(1M)
All times are GMT -4. The time now is 09:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy