There is a knowledge base article on the EqualLogic Support site that explains why the OS will display the actual volume size and the array has a different measurement. (Onced logged in to the support site, go to the KB, and do a search on “ARRAY: GUI space usage differs from what the OS shows”
In short, the array is a block level device, and has no knowledge of the OS file system. As the application data grows these are writes to the array. If later the application frees up space, the space is not marked as unused in the PS Series GUI, and is the reason for the difference in views between the OS/file system and the PS Series GUI.
Regarding the use of Thin Provision volumes, it depends a several factors, the attached document has some info you may find useful.
Joe S586
9 Technologist
•
729 Posts
1118
1
Posted July 6th, 2012 14:00
There is a knowledge base article on the EqualLogic Support site that explains why the OS will display the actual volume size and the array has a different measurement. (Onced logged in to the support site, go to the KB, and do a search on “ARRAY: GUI space usage differs from what the OS shows”
In short, the array is a block level device, and has no knowledge of the OS file system. As the application data grows these are writes to the array. If later the application frees up space, the space is not marked as unused in the PS Series GUI, and is the reason for the difference in views between the OS/file system and the PS Series GUI.
Regarding the use of Thin Provision volumes, it depends a several factors, the attached document has some info you may find useful.
-joe
1 Attachment
tr1031-thin-provisioning-v2.pdf
tr1031-thin-provisioning-v2.pdf