Thank you very much! Works like a charm, except for one thing: I gave my
clients the MDS caps 'allow rws path=<subvolume path>' to also be able
to create snapshots from the client, but `mkdir .snap/test` still returns
mkdir: cannot create directory ‘.snap/test’: Operation not permitted
Do you have an idea what might be the issue here?
Best regards,
Jonas
PS: A happy new year to everyone!
On 23.12.22 10:05, Kai Stian Olstad wrote:
On 22.12.2022 15:47, Jonas Schwab wrote:
Now the question: Since I established this setup more or less through
trial and error, I was wondering if there is a more elegant/better
approach than what is outlined above?
You can use namespace so you don't need separate pools.
Unfortunately the documentation is sparse on the subject, I use it
with subvolume like this
# Create a subvolume
ceph fs subvolume create <filesystem name> <subvolume name>
--pool_layout <pool name> --namespace-isolated
The subvolume is created with namespace fsvolume_<subvolume name>
You can also find the name with
ceph fs subvolume info <filesystem name> <subvolume name> | jq -r
.pool_namespace
# Create a user with access to the subvolume and the namespace
## First find the path to the subvolume
ceph fs subvolume getpath <filesystem name> <subvolume name>
## Create the user
ceph auth get-or-create client.<username> mon 'allow r' osd 'allow
rw pool=<pool name> namespace=fsvolumens_<subvolume name>'
I have found this by looking at how Openstack does it and some trial
and error.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
