mgerdts commented on this pull request.
> Consequently, writes to a sparse volume can fail with .Er ENOSPC when the pool is low on space. For a sparse volume, changes to .Sy volsize are not reflected in the reservation. +A volume that is not sparse is said to be +.Qq thick provisioned . +A sparse volume can become thick provisioned +by setting the reservation to Yeah, I was unsure about that. Other places mention reservation in a generic context (without `.Sy`) to refer to either. I think that changing to `refreservation` will cause less confusion, so will go with that. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/592#discussion_r175522179 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/discussions/Tcf29132d758782be-M9dbc9310732f7af4b7b82911 Delivery options: https://openzfs.topicbox.com/groups
