I'm not sure when that'll happen -- supporting partial usage isn't
something we're targeting right now. Most users are segregated into
one kind of client (userspace or kernel).
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
On Wed, Apr 9, 2014 at 12:10 PM, Michael Nelson wrot
Actually my intent is to use EC with RGW pools :). If I fiddle around with
cap bits temporarily will I be able to get things to work, or will
protocol issues / CRUSH map parsing get me into trouble?
Is there an idea of when this might work in general? Even if the kernel
doesn't support EC pool
This flag won't be listed as required if you don't have any erasure
coding parameters in your OSD/crush maps. So if you aren't using it,
you should remove the EC rules and the kernel should be happy.
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
On Tue, Apr 8, 2014 at 6:08 PM
On Tue, Apr 8, 2014 at 4:50 PM, Michael Nelson wrote:
> I am trying to mount CephFS from a freshly installed v0.79 cluster using a
> kernel built from git.kernel.org:kernel/git/sage/ceph-client.git
> (for-linus a30be7cb) and running into the following dmesg errors on mount:
>
> libceph: mon0 198.1
I am trying to mount CephFS from a freshly installed v0.79 cluster using a
kernel built from git.kernel.org:kernel/git/sage/ceph-client.git
(for-linus a30be7cb) and running into the following dmesg errors on mount:
libceph: mon0 198.18.32.12:6789 feature set mismatch, my 2b84a042aca < server's
