By default, GlusterFS does mount even deactivated snapshot(s) under /run/gluster/snaps. Since we do have a mount, there is a possibility that some process may access the mount, causing issues when trying to umount the volume for instance when deleting the snapshot.
Since in Container Native Storage everything is automated, the snapshot deletion failure will cause problems such as reaching the maximum limit of snapshots or stale snapshots being present because of the above issue.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.