- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: SAN/iQ's reclaim feature using ESXi 4.0
StoreVirtual Storage
1753481
Members
4723
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО11-16-2010 12:48 PM
тАО11-16-2010 12:48 PM
SAN/iQ's reclaim feature using ESXi 4.0
I read here (http://www.ostailors.com/docs/servers_storage/thin_provisioning.pdf) that SAN/iQ automatically reclaims zeroed blocks from thin provisioned volumes. We are running vSphere 4.0 with VMFS3 data stores that apparently do not automatically zero-out deleted files. I've read all kinds of crazy ideas for reclaiming unused space but nothing definitive from HP. Does anyone have any experience reclaiming space from a VMFS data store on a thin provisioned Lefthand volume? We have a few VM's that are going to be deleted and before I do so I want to know if it's a good idea to zero-out the virtual disks before actually deleting. From what I could find it looks like Lefthand will reclaim the vast majority of the space taken up by the vmdk file when it's zeroed out but if I just delete it straight from the vSphere client that space won't be reclaimed by the SAN. Thanks for anything anyone has on the subject.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2010 07:53 PM
тАО11-16-2010 07:53 PM
Re: SAN/iQ's reclaim feature using ESXi 4.0
I think you are misunderstanding the statement:
Here's the quote:
"When you decide to thin provision a volume, it├в s as easy as clicking a radio button in the SAN/iQ administration interface. Thin provisioning helps to keep your volumes thin over time by automatically reclaiming zero-filled blocks and returning them to the free storage pool."
This is true, however what this actually means is if you at first thick-provisioned a volume, and decided to later thin-provision it, it will reclaim any space that the underlying file system has not yet touched (zero-filled blocks). Once a file system (VMFS, NTFS etc.) has used a block, it is NEVER AGAIN considered a "zero-filled block". Since the file systems DO NOT go back and de-allocate blocks when files are deleted, you will always have a minimum used space equal to the "high water mark" or MAXIMUM blocks EVER used by the file system.
Currently the only way to reclaim VMFS datastore "empty" space would be to create a NEW VMFS Volume, migrate the VMs to the new datastore, and delete the old datastore.
Hope this clears things up for you.
Here's the quote:
"When you decide to thin provision a volume, it├в s as easy as clicking a radio button in the SAN/iQ administration interface. Thin provisioning helps to keep your volumes thin over time by automatically reclaiming zero-filled blocks and returning them to the free storage pool."
This is true, however what this actually means is if you at first thick-provisioned a volume, and decided to later thin-provision it, it will reclaim any space that the underlying file system has not yet touched (zero-filled blocks). Once a file system (VMFS, NTFS etc.) has used a block, it is NEVER AGAIN considered a "zero-filled block". Since the file systems DO NOT go back and de-allocate blocks when files are deleted, you will always have a minimum used space equal to the "high water mark" or MAXIMUM blocks EVER used by the file system.
Currently the only way to reclaim VMFS datastore "empty" space would be to create a NEW VMFS Volume, migrate the VMs to the new datastore, and delete the old datastore.
Hope this clears things up for you.
http://www.tdonline.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2010 09:02 PM
тАО11-16-2010 09:02 PM
Re: SAN/iQ's reclaim feature using ESXi 4.0
Thanks for the info, teledata! I guess that just goes to show you can't trust any old blog out there.
Do you know if this will change in SAN/iQ 9.0 + ESXi 4.1 VAAI?
Do you know if this will change in SAN/iQ 9.0 + ESXi 4.1 VAAI?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP