- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- 3PAR LUN does not shrink in size, when VMware virt...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2013 07:09 AM
01-17-2013 07:09 AM
Hi,
I have VMware vCenter Server version 5.1.0 build 799731 and all my ESXi hosts runs ESXi version 5.1.0 build 799733.
As a SAN I am having 3PAR storage (3PAR InForm Management Console version 4.2.1.3).
I have created a LUN on 3 TB size as a Virtuel Thinly Provisioned LUN and 3PAR reports that Used User Space is 2.6 TB in size.
If I browse the LUN in VMware, I only have servers on the LUN with 1 TB in size and nothing more.
As a test, I have tried to vMotion move on server with a storage usage on 150 GB to another LUN and the other LUN grows correct in size, but the old LUN does not shrink in size.
Should 3PAR not shrink the disk in size, when VMware does not use the disk?
What number should I use as valid? the storage usage in 3PAR or in VMware?
Kind regards,
Carl-Marius
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2013 06:38 AM
01-18-2013 06:38 AM
SolutionDo you have Zero Detect enabled on the Thin Provisioned Virtual Volume? 'Enabled' has not been the default setting in the past. You may need to enable Zero Detect on the TPVV, then use a vSphere function to zero out free space in the datastore. Create (and delete) a large "Eager Zeroed Thick” (EZT) virtual disk, or "vmkfstools -y <n>% <datastore>".
Check the HP 3PAR StoreServ Storage and VMware vSphere 5 best practices document at http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA4-3286ENW.pdf
----------
If my post was useful, clik on my KUDOS! "White Star" !
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2013 05:07 AM
01-23-2013 05:07 AM
Re: 3PAR LUN does not shrink in size, when VMware virtual servers gets migrated to another LUN?
Hi Sheldon Smith,
Thank you for your answer, this is the answer on my issue! :-)
Kind regards,
Carl-Marius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2015 01:16 AM
02-26-2015 01:16 AM
Re: 3PAR LUN does not shrink in size, when VMware virtual servers gets migrated to another LUN?
Sadly this does not work anymore with vsphere 5.5
Due to performance issues you have to use the CLI now to start the process if "UNMAP" in VMWare
See http://vmw.re/1BfDOG3
In ESXi 5.5, vmkfstools -y is deprecated and has been replaced by the esxcli storage vmfs unmap command. However, issuing UNMAP is still disabled by default. Space reclamation can be done manually by running the esxcli storage vmfs unmap command. For more information, see Using esxcli in vSphere 5.5 to reclaim VMFS deleted blocks on thin-provisioned LUNs (2057513)