vSphere5x存储空间回收--用DELLEQL为例子.docxVIP

vSphere 5.x 存储空间回收--用DELL EQL 为例子近日，公司内部很多案子都讨论到空间回收这个话题起因，是客户在EQL （其他存储也一样）的管理界面看到的可用空间和vmware内部看到的不一致原因，EQL 是block （块）级别的存储，它不是一个文件系统；当一个文件被删除了，ESXi没有告诉底层把这文件占用的块清除掉；这个新的（相对于esxi 4)名词叫“unmap”，在esxi 5.x已经开始支持用一个工具手工的回收这些空间。所以在esxi看到的空间和存储上显示的不同。一般情况下，esxi看到的可用空间是比存储上看到的可用空间要大??解决办法或者说工具在帖子后面ARRAY: GUI space usage differs from what the OS showsQ: Why is there a difference between what my file system shows as space used and what the PS array GUI shows for in-use for the volume??A: The PS array is block-storage, and only knows about areas of a volume that have ever been written. The PS Series GUI reports this information for each volume. Volume allocation grows automatically due to application data writes. If later the application frees up space, the space is not marked as unused in the PS Series GUI. Hence the difference in views between the OS/file system and the PS Series GUI.?With thin provisioned volumes, this perception can be more pronounced.?Thin provisioning is a storage virtualization and provisioning model that allows administrators to logically allocate large addressable storage space to a volume, yet not physically commit storage resources to this space until it is used by an application. For example, using thin provisioning you can create a volume that an application views as 3 TB, while only allocating 300 GB of physical storage to it. As the operating system writes to the volume, physical disk space is allocated to the volume by the storage array. This physical disk space is taken from the available free space in the pool automatically and transparently. As a result, less physical storage is needed over time, and the stranded storage problem is eliminated. The administrator enjoys management benefits similar to over-provisioning, yet maintains the operational efficiencies of improved physical storage utilization. This more efficient use of physical storage resources typically allows an organization to defer or reduce storage purchases.?So Thin provisio