Thanks for pointing that out, since it is incorrect for (semi-)modern QEMUs. All configuration starts and the Ceph defaults, are overwritten by your ceph.conf, and then are further overwritten by any QEMU-specific override. I would recommend retesting with "cache=writeback" to see if that helps.
On Fri, Oct 21, 2016 at 2:10 PM, Pavan Rallabhandi <prallabha...@walmartlabs.com> wrote: > The VM am testing against is created after the librbd upgrade. > > Always had this confusion around this bit in the docs here > http://docs.ceph.com/docs/jewel/rbd/qemu-rbd/#qemu-cache-options that: > > “QEMU’s cache settings override Ceph’s default settings (i.e., settings that > are not explicitly set in the Ceph configuration file). If you explicitly set > RBD Cache settings in your Ceph configuration file, your Ceph settings > override the QEMU cache settings. If you set cache settings on the QEMU > command line, the QEMU command line settings override the Ceph configuration > file settings.” > > Thanks, > -Pavan. > > On 10/21/16, 11:31 PM, "Jason Dillaman" <jdill...@redhat.com> wrote: > > On Fri, Oct 21, 2016 at 1:15 PM, Pavan Rallabhandi > <prallabha...@walmartlabs.com> wrote: > > The QEMU cache is none for all of the rbd drives > > Hmm -- if you have QEMU cache disabled, I would expect it to disable > the librbd cache. > > I have to ask, but did you (re)start/live-migrate these VMs you are > testing against after you upgraded to librbd v10.2.3? > > -- > Jason > > > -- Jason _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
