|
Kernel 4.13+ (i tested up to 4.18) missed some non-essential feature (explained by a Ceph dev on this ML) that was in Luminous, so they show up as Jewel, but otherwise they're fully compatible with upmap. We have a few hundred nodes on the kernel client with CephFS, and we also run balancer with upmap mode on those clusters successfully. From: ceph-users <ceph-users-bounces@xxxxxxxxxxxxxx> on behalf of Stefan Kooman <stefan@xxxxxx>
Sent: Friday, 9 November 2018 3:10:09 AM To: Ilya Dryomov Cc: ceph-users Subject: Re: CephFS kernel client versions - pg-upmap 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 ... Gr. Stefan -- | BIT BV https://protect-au.mimecast.com/s/40snCQnzDmsny8BOsxWQtx?domain=bit.nl Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / info@xxxxxx _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
