Using "profile rbd-read-only" with krbd wouldn't work unless you are
on kernel 5.5 or later. Prior to 5.5, "rbd map" code in the kernel
did some things that are incompatible with "profile rbd-read-only",
such as establishing a watch on the image header and more.
This was overlooked because it is
Yeah, file systems rarely really do a read-only mount without providing
some very obscure options, no idea about xfs specifically.
Suggestion: use a keyring with profile rbd-read-only to ensure that it
definitely can't write when mapping the rbd. xfs might just do the right
thing automatically whe
Thanks Janne. I actually meant that the RW mount is unmounted already -
sorry about the confusion.
- Shridhar
On Mon, 4 May 2020 at 00:35, Janne Johansson wrote:
> Den mån 4 maj 2020 kl 05:14 skrev Void Star Nill >:
>
>> One of the use cases (e.g. machine learning workloads) for RBD volumes in
Den mån 4 maj 2020 kl 05:14 skrev Void Star Nill :
> One of the use cases (e.g. machine learning workloads) for RBD volumes in
> our production environment is that, users could mount an RBD volume in RW
> mode in a container, write some data to it and later use the same volume in
> RO mode into a
Hello Brad, Adam,
Thanks for the quick responses.
I am not passing any arguments other than "ro,nouuid" on mount.
One thing I forgot to mention is that, there could be more than one mount
of the same volume on a host - I dont know how this plays out for xfs.
Appreciate your inputs.
Regards,
Sh
Are you mounting the RO with noatime?
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
I'm pretty sure to XFS, "read-only" is not quite "read-only." My
understanding is that XFS replays the journal on mount, unless it is also
mounted with norecovery.
--
Adam
On Sun, May 3, 2020, 22:14 Void Star Nill wrote:
> Hello All,
>
> One of the use cases (e.g. machine learning workloads) fo
