Here it mentions that sparse files are supported: https://docs.netapp.com/us-en/ontap/nfs-admin/ontap-support-nfsv42-concept.html
Sparse files are a requirement for ALLOCATE/DEALLOCATE afaik: https://www.rfc-editor.org/rfc/rfc7862.html#section-15.4
#Does ONTAP support NFSv4.2 DEALLOCATE?
cosmic vector
Proxmox supports NFSv4.2 which customer wants to use. Sparse files stay "sparse" when being created on a local disk and then being moved to the NetApp NFS-datastore.
But triyng to "TRIM"/DEALLOCATE there does not seem to work. The DEALLOCATE NFSv4 call only gets a NFS4ERR_IO reply.
topaz island
just a wild guess, but did you try enabling vstorage?
potent mural
supported in 9.10.1
if only cluster is at 9.10.1 and if the v4.1 option is on
Whole file unreservation (deallocate + unreserve) supported. Partial range hole punching supported. This means blocks will be freed but not unreserved. Partial range unreservation is not supported.
cosmic vector
just a wild guess, but did you try enabling vstorage?
will check, good point, the customer actually created a new SVM for the tests so could be possible
cosmic vector
Whole file unreservation (deallocate + unreserve) supported. Partial range hole...
I don't understand this: What is the difference between these two?
"Partial range hole punching supported."
"Partial range unreservation is not supported."
potent mural
I think you would have to look in the RFC for more information, but I think hole punching is for creating new files while unreservation is modifying existing files
cosmic vector
I just did. 🙂
When the RFC talks about "hole punching" always only DEALLOCATE is mentioned. So hole punching = NFSv4.2 operation DEALLOCATE.
The same with the term "unreserve", it's always about DEALLOCATE.
There are no hole punching or unreserve commands. There only is DEALLOCATE in NFSv4.2.
And it says for DEALLOCATE: "Whenever a client wishes to unreserve space for a region in a file"
I'm a bit confused, especially since the docs mention that sparse files are only supported with 9.12.1: https://docs.netapp.com/us-en/ontap/nfs-admin/ontap-support-nfsv42-concept.html
potent mural
9.12.1 would certainly seem to be best then
