HPE Storage Users Group
https://3parug.com/

.<index>] <size>[g|G|t|T]
https://3parug.com/viewtopic.php?f=18&t=3132
Page 1 of 1

Author:  squant [ Mon Mar 18, 2019 3:04 pm ]
Post subject:  .<index>] <size>[g|G|t|T]

what is the difference in the g|G|t|T. when mirroring a lun the same size is coming up to small on the 3par. Not sure why or how to get around it. the quick fix is make the 3par lun 1gig larger but that doesn't seem to be the only solution.

Author:  MammaGutt [ Mon Mar 18, 2019 3:18 pm ]
Post subject:  Re: .<index>] <size>[g|G|t|T]

According to CLI reference guide g and G is GB and t and T is TB.

What are you mirroring? 3PAR to 3PAR with remote copy or host-based mirror where the other copy is stored on something else? If the latter, what is host OS, the other storage array and size of volume on that?

Author:  squant [ Tue Mar 19, 2019 10:03 am ]
Post subject:  Re: .<index>] <size>[g|G|t|T]

Yes, I am aware g and G is GB. I'm assuming the conversion is different otherwise why would there be 2 options. Its a 100GB LUN presented from XP24000 on an OpenVMS system being mirrored to a 100GB LUN on HP3par. However the VMS system sees the 3par lun as to small. The fix is making it 101GB but that just doesn't seem right.

Author:  MammaGutt [ Tue Mar 19, 2019 11:30 am ]
Post subject:  Re: .<index>] <size>[g|G|t|T]

squant wrote:
Yes, I am aware g and G is GB.


Before I checked the CLI guide I actually thought one was GiB :)

Without knowing OpenVMS, do you have any disk tool to list the exact size of the volume? As you've experienced not all storage arrays define size in the same way.

Author:  ailean [ Wed Mar 20, 2019 4:40 am ]
Post subject:  Re: .<index>] <size>[g|G|t|T]

What model and os version is your 3PAR?

We noticed something recently when migrating from an older 10400 3PAR with 3.2.2MU4 to a new 9450 3PAR with 3.3.1MU3, we had a 100G LUN on the 10400 and a 100G LUN on the 9450. It appears the geometry defaults changed even within 3PAR models/versions as the heads/cylinders etc were different and the number of bytes/sectors did not match (the new LUN being a little smaller) so trying to mirror a byte for byte copy in Solaris complained. :roll:

EDIT: There are options at the CLI I think to manually specify the LUN geometry which might get around this but I've avoided going there and our UNIX admins seem to have worked around the issue at their end without me having to tweak LUN sizes.

Author:  squant [ Thu Mar 21, 2019 1:01 pm ]
Post subject:  Re: .<index>] <size>[g|G|t|T]

Its a 7400.

Page 1 of 1 All times are UTC - 5 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/