OTV version 9.13P1 seems to have an issue where if you try to create a datastore (I only tested iSCSI based) over 16TB, it complains "like in the old days"... if you then create the datastore at say 10TB, and afterwards resize it (with OTV) to say 20TB, it works OK... guess this is an overlooked bug or something?
#ONTAP Tools LUN size issue?
low portal
This "might" be a problem if you would like to create a datastore of say 200TB... because I think there is still the good old issue with expanding LUNs over their original size (it is 10 times the original?)
hidden flume
ESXi used to complain about performance issues if the LUN size is over a certain point too. I don't remember if they ever increased it, but you don't want to exceed that.
low portal
The point is that there is a bug in the OTV software that does not allow you to create LUNs larger than 16TB initially... this will cause an issue if you wanted to create a LUN of way 200TB... you would not be able to do it because of the LUN resize "issue" where you can only expand your LUN by 10 times its initial size... granted this isn't an issue for us, but it might be for someone else...
tawdry mauve
I don't think the resizing is still an issue in recent ONTAP versions. For example my 9.14.1 cluster shows this:
cl1::*> lun geometry -vserver TEST
Vserver Name: TEST
Path: /vol/luns/test.lun
Bytes per Sector: 512
Sectors per Track: 0
Tracks per Cylinder: -
Sectors per Cylinder: 0
Number of Cylinders: 0
Max Resize Size: 128TB
Number of Sectors: 2097152
Cylinder Size: 256MB
Device Size: 1GB
Note the current size (I just created the lun with a size of 1gb) and the "Max Resize Size", which is 128TB
robust delta
stone glade
tawdry mauve
yeah the limit for ESXi is 64T but that was not the issue here if I understood correctly? The question was about the 10x limit for resizing LUNs, which doesn't exist anymore