Yes, that is exactly what it means, but that's fine.  The array doesn't tell the OS, it's "full".  The OS, will reuse blocks as needed.  It's the OS that knows what blocks are available. It does that through its allocation table.  The array simply responds to requests from the server.   In SCSI when writing you typically see the SCSI command  "WRITE10".  That has the block number to save it to and the data to put there.  The array just does as it's told.   It doesn't care that it's already been written to.   With the new UNMAP SCSI command, the OS can now pass that info along to the storage device.  It basically says  UNMAP/FREE block X  For VMware, It's part of the VAAI suite introduced in ESX v4.1.    Here's and FAQ on it. kb.vmware.com/.../search.do
Hi All, couple of questions.  Wondering why I see very different space available numbers in the EQL web gui vs. vsphere client?  In the EQL gui, I'm showing 330GB free, but in vsphere client, I'm showing 674GB free.  What also appears to be occurring is that when I use up space on my EQL volume and then later free up that space, it does not appear that EQL is releasing the space.  e.g., I svmotion a large vm to volume 1 and Dell GUI reports the additional space used.  I then move the same system to volume 2, but Dell GUI still shows the same space used on volume 1?
PS4000 Volume space not releasing?