- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Docker Container Integration
- >
- esxcli storage vmfs unmap
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
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
10-23-2017 11:10 AM
10-23-2017 11:10 AM
esxcli storage vmfs unmap
I am running esxi 6.0 and would like to reclaim some space by running this command on my nimble luns
is there a specific ocmmand I should run as far as the reclaimable units?
esxcli storage vmfs unmap 4000 ?
what number should i use?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2017 10:38 AM
11-01-2017 10:38 AM
Re: esxcli storage vmfs unmap
ESXi 5.5 and later:
In ESXi 5.5, VMware have simplified the process by not requiring a lookup of the datastore device code, only a datastore name is required. Also, rather than creating a temporary ‘balloon file’ that processes all the requested unmaps in one swing (that can lead to the volume filling up if a too high a percentage is specified), unmaps are issued to the target volume in a steadier fashion.
- Connect to the ESXi hosts CLI via SSH. SSH access may need enabling through the vSphere clients security settings.
- Obtain the datastore name as shown in the vSphere client that the space discrepancy issue is seen on, and begin the unmap process using the following command:
# esxcli storage vmfs unmap -l <datastore-name>
OR: If the array is utilizing a large percentage please consider unmaping a small amount of space in each iteration using the -n flag.
# esxcli storage vmfs unmap -n <amount of blocks> -l <datastore-name>
Example:
# esxcli storage vmfs unmap -n 20 -l datastore1
- This command will unmap the entire datastore at 20MB per unmap operation, while the script is running.
By default, the space reservation for the temporary files depends on the block size of the underlying VMFS file system (the default is --reclaim-unit=200):
- 200 MB for 1 MB block under VMFS3 / VMFS5
- 800 MB for 4 MB block under VMFS3
- 1600 MB for 8 MB block under VMFS3