the directory the client is restricted too (e.g., ``/home/user``)
or something nested beneath it.
+ In case of a kernel client, it needs to have access to the parent
+ of the directory inode on which quotas are configured in order to
+ enforce them. If quota is configured on a directory path
+ (e.g., ``/home/volumes/group``), the kclient needs to have access
+ to the parent (e.g., ``/home/volumes``).
+
+ An example command to create such an user is as below::
+
+ $ ceph auth get-or-create client.guest mds 'allow r path=/home/volumes, allow rw path=/home/volumes/group' mgr 'allow rw' osd 'allow rw tag cephfs metadata=*' mon 'allow r'
+
+ See also: https://tracker.ceph.com/issues/55090
+
#. *Snapshot file data which has since been deleted or changed does not count
towards the quota.* See also: http://tracker.ceph.com/issues/24284