All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Barbe <laurent@ksperis.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: CEPH_FEATURE_OSD_CACHEPOOL always required when osd cache pool exist ?
Date: Tue, 21 Jan 2014 09:28:00 +0100	[thread overview]
Message-ID: <52DE2F90.9030201@ksperis.com> (raw)

Hi all,

About 0.75, when I created cache pool, kernel client like rbd or cephfs 
make error "feature set mismatch". (Even if the device is not on the 
cached pool)

$ rbd map rbd/myrbd    => OK

$ ceph osd pool create otherpool1 100 100
$ ceph osd pool create otherpool2 100 100
$ ceph osd tier add otherpool1 otherpool2
$ ceph osd tier cache-mode otherpool2 writeback

$ rbd map rbd/myrbd
kern log >> libceph: mon2 10.2.0.90:6789 feature set mismatch, my 
4a042a42 < server's 84a042a42, missing 800000000

Does the commit 
https://github.com/ceph/ceph/commit/431a13eb370310a383abceeb509fe204a519e087
fix this ?


Regards,
Laurent Barbe

             reply	other threads:[~2014-01-21  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21  8:28 Laurent Barbe [this message]
2014-01-21  9:46 ` CEPH_FEATURE_OSD_CACHEPOOL always required when osd cache pool exist ? Ilya Dryomov
2014-01-21 10:03   ` Laurent Barbe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52DE2F90.9030201@ksperis.com \
    --to=laurent@ksperis.com \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.