Hi Jonas,
On Mon, Jan 2, 2023 at 10:52 PM Jonas Schwab
wrote:
>
> Thank you very much! Works like a charm, except for one thing: I gave my
> clients the MDS caps 'allow rws path=' to also be able
> to create snapshots from the client, but `mkdir .snap/test` still returns
> mkdir: cannot crea
One side affect of using sub volumes is that you can then only take a snap
at the sub volume level, nothing further down the tree.
I find you can use the same path on the auth without the sub volume unless
I’m missing something in this thread.
On Mon, Jan 2, 2023 at 10:21 AM Jonas Schwab <
jonas.
Thank you very much! Works like a charm, except for one thing: I gave my
clients the MDS caps 'allow rws 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
You could try creating Subvolumes as well:
https://docs.ceph.com/en/latest/cephfs/fs-volumes/
As usual, ceph caps and data layout semantics apply to Subvolumes as well.
On Thu, Dec 22, 2022 at 8:19 PM Jonas Schwab <
jonas.sch...@physik.uni-wuerzburg.de> wrote:
> Hello everyone,
>
> I would like
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 docum
