Re: 7.2 load source size Was: IBM i 7.1 Technology Refresh 7 available Nov. 15-CLARIFICATION on POWER5

And if you want to get picky.

On Frankie where the drives truly are 17GB physical units the LS disk is 15355 Bytes as it has lost space to RAID. Disks there that do NOT have any stripe data report as 17548 MB.

On our iDevCloud partitions (POWER7 pure virtual) the drives we build are sized NWSSIZE(18865). When displayed in the virtual partition the disks report as 17583 MB or 'just a fuzz' bigger than a physical 17GB drive.

With that math NWSSIZE(75460) should turn into a 70GB true drive.

All in all though I'm guessing we're really arguing over nits here. :-)

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 10/16/2013 10:41 PM, Pete Massiello - ML wrote:

Sue,

I see your recommendation of 79565.

Yet, this IBM link http://www-01.ibm.com/support/docview.wss?uid=nas8N1013717 says The smallest load source capacity allowed is 17 GB (document is discussing 6.1 & 7.1). In order to have a virtual disk of size 17 GB, it must be created as a 19.2 GB drive. Technically the system will allow a smaller disk size when using virtual disks; however, this will cause problems later--for example, when you go to upgrade to the next release and try to expand the LIC space.

Since a 17GB drive is referring to the 17.5 GB drives, which is 1/4 that of a 70GB drive, why wouldn't you multiple 19.2GB by 4 and get 76,800 when using the CRTNWSSTG command?

Thanks

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Wednesday, October 16, 2013 7:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: 7.2 Was: IBM i 7.1 Technology Refresh 7 available Nov. 15-CLARIFICATION on POWER5

Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> wrote on Wed, 16 Oct 2013 23:01:23 GMT:

The LPARs are anywhere between 15 and 30 virtual drives all at 35GB
right now. I'm going to set up at least two or more vSCSI controllers
on each, so we can vitrualize tape/dvd on one then have the others for
storage.

With that quantity of virtual devices, doubling all the VSCSI units to 70G would be lots of storage. I think in this specific case, 70G load source and then specifying *ENDALC after you get LIC, QSYS, QUSRSYS, QGPL loaded and balanced would be an appropriate plan.

When you create the load source unit via CRTNWSSTG, make sure you don't specify 70000 "megabytes" as your size (NWSSIZE) because you won't really end up with 70 GB. You need to specify as 71680 to really get to 70 GB. However, don't forget the 512- byte translation makes the i client LPAR see this unit as 11% smaller, so it would end up at approximately 62 GB.

To have the client see a 70 GB (or slightly larger) unit, you want to define at 79565 megabytes in the CRTNWSSTG command.

--
Sue
IBM Americas Advanced Technical Skills (ATS) Power Systems Rochester, MN
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.