Can anyone provide experiences with storage devices that use thin provisioning? I’ve been testing a few on them and I run into problems with the storage device incorrectly reporting the usage allocation after the files are deleted. I see this reference in the GPFS FAQ, but I’m looking for some real-world experiences.
Most flash devices use thin provisioning internally. Reference here: https://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSFKCN/com.ibm.cluster.gpfs.doc/gpfs_faqs/gpfsclustersfaq.html#thinprov Q4.12: What are the considerations for using thinly provisioned or compressed volumes with GPFS? A4.12: While it is possible to use thinly provisioned (compression constitutes a form of thin provisioning) volumes with GPFS, there are some important configuration aspects that must be considered. Placing GPFS metadata on an NSD backed by a thinly provisioned volume is dangerous and unsupported. If the real disk space backing a thinly provisioned virtual volume is exhausted, there is a possibility of a write to a previously allocated disk sector failing. If this volume hosts GPFS metadata, in certain scenarios this could make a GPFS file system temporarily or even permanently unavailable. Placing GPFS data on a thinly provisioned volume is supported, but with certain limitations. Specifically, if the real disk space backing a thinly provisioned virtual volume is exhausted, a failing data write could make the GPFS file system temporarily unavailable. Since at present GPFS does not communicate block deallocation events to the block device layer, freeing space on the file system layer does not free up space on the block device layer. Thus it is possible for the efficiency of thin provisioning to degrade over time, as blocks as allocated and freed. Bob Oesterlin Sr Storage Engineer, Nuance HPC Grid
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
