On 2019-07-09T16:32:22, Mattia Belluco wrote:
> That of course in my case fails with:
> Error EPERM: cannot set require_min_compat_client to luminous: 29
> connected client(s) look like jewel (missing 0x800); 1
> connected client(s) look like jewel (missing 0x800); add
> -
On Tue, Jul 9, 2019 at 4:32 PM Mattia Belluco wrote:
> Hi Paul,
>
>
> Should I just go ahead?
yes
> My guess is that those clients (that are CephFS
> clients using the kernel driver) will not be able to mount the
> filesystem anymore.
>
no, that will continue to work because it only blocks c
Hi Paul,
thanks for the quick reply. I am still a bit puzzled as the
documentation states:
"To allow use of the feature, you must tell the cluster that it only
needs to support luminous (and newer) clients with:
ceph osd set-require-min-compat-client luminous"
That of course in my case fails wi
Yes, upmap will work with 4.15. The Ceph kernel client is a completely
independent implementation from the user space client, so you can't really
map it to any specific features. It has some Luminous features but lacks
others.
Paul
--
Paul Emmerich
Looking for help with your Ceph cluster? Conta
Hello ml,
I have been looking for an updated table like the one you can see here:
https://ceph.com/geen-categorie/feature-set-mismatch-error-on-ceph-kernel-client/
Case in point we would like to use upmap on our ceph cluster (currently
used mainly for CephFS) but `ceph feature` return:
"client
