Following on from my previous post, on working with scalable VGs.   https://www.ibm.com/developerworks/mydeveloperworks/blogs/cgaix/entry/working_with_aix_scalable_volume_groups1?lang=en   You may find yourself in a situation where you’d like to convert a VG to scalable.   For example, you might start off with a normal VG i.e. one that can support a maximum of 256 LVs and 32 PVs.   # mkvg -s 512M -y myvg hdisk5 myvg   # lsvg myvg VOLUME GROUP:        myvg                      VG IDENTIFIER:   00f6027300004c0000000133aa24d1f6 VG STATE:... [More]

Marcações:  aix lvm pv chvg gibson convert -g mkvg manager scalable hdisk chris conversion group groups volume max vg lv physical logical

Scalable volume groups first appeared in AIX 5.3. They allow a maximum of 1024 physical volumes and 4096 logical volumes per volume group. This is pretty cool for large systems. In the ‘old days’ we could end up in situations where we’d reached the maximum PV count (32 or 128) for a VG and have to create a new VG to work around the issue.   I use scalable VGs for all my new large AIX system builds.   The following command will create a scalable VG (named svg ) on hdisk4. You’ll notice that MAX PVs is set to 1024 and MAX LVs is set to 256.... [More]

Marcações:  gibson aix vg manager lvm pv chris chvg hdisk max physical lv scalable groups group mkvg logical volume

Here’s a question I received recently, that relates to virtual SCSI hdisk path priority.   Hi, Chris, I use MPIO for our virtualization environment. I'd like to check which path is currently used. How can I get the result? For example:   [nim:/]# lspath Enabled hdisk0 vscsi0 Enabled hdisk0 vscsi1 Enabled hdisk2 vscsi2 Enabled hdisk1 vscsi1 Enabled hdisk1 vscsi0 Enabled hdisk3 vscsi2 Enabled hdisk2 vscsi3 Enabled hdisk3 vscsi3   How can I determine vscsi0 or vscsi1 is currently carrying data through VIOS and VIOC. Thanks a lot!   By default... [More]

Marcações:  priority aix hdisk gibson vios vscsi chris