.Deleting a subvolume clone is no longer allowed for certain clone states Previously, if you tried to remove a subvolume clone with the force option when the clone was not in a `COMPLETED` or `CANCELLED` state, the clone was not removed from the index tracking the ongoing clones. This caused the corresponding cloner thread to retry the cloning indefinitely, eventually resulting in an `ENOENT` failure. With the default number of cloner threads set to four, attempts to delete four clones resulted in all four threads entering a blocked state allowing none of the pending clones to complete. With this release, unless a clone is either in a `COMPLETED` or `CANCELLED` state, it is not removed. The cloner threads no longer block because the clones are deleted, along with their entry from the index tracking the ongoing clones. As a result, pending clones continue to complete as expected.