On Thu, Nov 8, 2018 at 5:10 PM Stefan Kooman <stefan@xxxxxx> wrote:
>
> Quoting Stefan Kooman (stefan@xxxxxx):
> > I'm pretty sure it isn't. I'm trying to do the same (force luminous
> > clients only) but ran into the same issue. Even when running 4.19 kernel
> > it's interpreted as a jewel client. Here is the list I made so far:
> >
> > Kernel 4.13 / 4.15:
> > "features": "0x7010fb86aa42ada",
> > "release": "jewel"
> >
> > kernel 4.18 / 4.19
> > "features": "0x27018fb86aa42ada",
> > "release": "jewel"
>
> On a test cluster with kernel clients 4.13, 4.15, 4.19 I have set the
> "ceph osd set-require-min-compat-client luminous --yes-i-really-mean-it"
> while doing active IO ... no issues. Remount also works ... makes me
> wonder how strict this "require-min-compat-client" is ...
It's there to stop you from accidentally enabling new features that
some of your clients are too old for. In its current form it's quite
easy to bypass but I think there are plans to make it stronger in the
future.
You didn't actually enable any new features by bumping it to luminous.
But you shouldn't see any issues even if you go ahead and do that (e.g.
put the balancer in upmap mode) because your clients are new enough.
Thanks,
Ilya
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
