From the article:
I think it's not true.Hole punching as it pertains to file-systems is marking a portion of a file as being no longer needed and can then be reclaimed.
Afaik hole punching is about _virtually_ allocating space for a big file but physically only doing so when one is writing to it and only as much as has been written.
E.g. when you create a vmware virtual image of like 10GB for a Linux OS that uses only like 4GB when fully installed you'll actually be using just 4GB on your HDD while the vmware installed image file ".vmdk" claims/thinks it's 10GB.
This also has some drawbacks, like when the guest OS tries to use the rest of the "free" space while the disk is already full.