Users don't know the name of the filesystem to use when mounting shares.

Ceph supports multiple cephfs filesystems since the Pacific release. This functionality allows configuring separate file systems with full data separation on separate pools. Alongside data separation, each filesystem has its own metadata pools as well as metadata server/s. OpenStack Manila users benefit from this level of isolation by mapping an isolated filesystem to a separate backend. This means that you could have multiple backends configured in Manila provisioning onto the same ceph cluster, but each within its own CephFS filesystem.

The CephFS driver permits this by the use of a configuration option: ``cephfs_filesystem_name``.

When the filesystem isn't called "cephfs", users/automation software will need to specify the filesystem name when mounting subvolumes (manila shares). This issue was discussed at the Oct 2023 (Caracal) PTG. One solution was for the driver to set the filesystem name as the share's metadata so users and automation tools can view this information.