VMware Cloud Community
rongageC
Contributor
Contributor
Jump to solution

Cannot expand datastore after expanding LUN size

Greetings:

I have an interesting problem happening with my ESXi server.  I have expaneded a LUN from 1.5T to 3T, rescanned the SAN from the host itself (not from vCenter), yet ESXi still reports the LUN size as 1.5T and not expandable.

SAN is an EMC VNX and Unisphere is indeed reporting the LUN size as 3T.  The VMFS on this LUN is at version 5.54.

I have done refreshes and rescans from a single host and nothing changes with regards to the size of the LUN as reported within VMware.  I can't imagine this being a fabric issue since the underlying data is still available and working.

Does anyone have any suggestions to try on this?

Ron

Tags (5)
1 Solution

Accepted Solutions
timdelier
Contributor
Contributor
Jump to solution

Do you have RecoverPoint setup for this LUN? I just ran into the same problem that you described, and found this article. It worked for me.

http://www.mikes.eu/index.php/how-to/254-how-to-resize-a-lun-that-is-already-replicated-by-emc-recov...

~Tim

View solution in original post

5 Replies
mrksiddiqui
Enthusiast
Enthusiast
Jump to solution

You have to increase the size manually. Review the document.

http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-501-storag...

If this helps answer your question please consider awarding points!
0 Kudos
timdelier
Contributor
Contributor
Jump to solution

Do you have RecoverPoint setup for this LUN? I just ran into the same problem that you described, and found this article. It worked for me.

http://www.mikes.eu/index.php/how-to/254-how-to-resize-a-lun-that-is-already-replicated-by-emc-recov...

~Tim

snootalope
Contributor
Contributor
Jump to solution

rongageC -- just curious what you ended up doing here to get this to work properly?  Thanks for any info (I'm revieowing the storage guide pdf..)

0 Kudos
rongageC
Contributor
Contributor
Jump to solution

We had a ReplicationPoint appliance and SRM tied to the LUN in question.  For other reasons not related to this problem, we had to completely restart our configuration of the ReplicationPoint and SRM and as a consequence, remove the LUN from the two services.  This allowed VMware to see the expanded LUN size and also allowed us to expand the datastore to fill the LUN without issue.

0 Kudos
snootalope
Contributor
Contributor
Jump to solution

Thanks for the reply, removing the LUN and readding has been my work around as well.  Was hoping maybe there was an easier way..

0 Kudos