It all depends on how you are creating your RBDs. Whatever your using is likely overriding the defaults and using a custom line in it's code.
What you linked did not say that you cannot turn on the features I mentioned. There are indeed some features that cannot be enabled if they have ever been turned off, but object-map is not one of those. You just need to enable them in the correct order so that the RBD can utilize them. What you quoted does indeed also show that some clients will be unable to read an RBD that has these features enabled if it is not new enough. Any kernel older than 4.9 cannot map an RBD with these features enabled.older versions of rbd-fuse can't map them. Same for librbd or anything else. Those features can be disabled and re-enabled. You do not have to create a new RBD and migrate the data across... unless you need something like deep-flatten which cannot be enabled if the RBD has ever existed without it enabled. On Fri, Jun 23, 2017 at 6:14 PM Massimiliano Cuttini <m...@phoenixweb.it> wrote: > What seems to be strange is that feature are *all disabled* when I create > some images. > While ceph should use default settings of jewel at least. > > Do I need to place in ceph.conf something in order to use default settings? > > > > > Il 23/06/2017 23:43, Massimiliano Cuttini ha scritto: > > I guess you updated those feature before the commit that fix this: > > https://github.com/ceph/ceph/blob/master/src/include/rbd/features.h > > As stated: > > // features that make an image inaccessible for read or write by > /// clients that don't understand them > #define RBD_FEATURES_INCOMPATIBLE (RBD_FEATURE_LAYERING | \ > RBD_FEATURE_STRIPINGV2 | \ > RBD_FEATURE_DATA_POOL) > > /// features that make an image unwritable by clients that don't understand > them > #define RBD_FEATURES_RW_INCOMPATIBLE (RBD_FEATURES_INCOMPATIBLE | \ > RBD_FEATURE_EXCLUSIVE_LOCK | \ > RBD_FEATURE_OBJECT_MAP | \ > RBD_FEATURE_FAST_DIFF | \ > RBD_FEATURE_DEEP_FLATTEN | \ > RBD_FEATURE_JOURNALING) > > > Some features are no-way back: if you downgrade you cannot restore anymore. > As stated here: https://bugzilla.redhat.com/show_bug.cgi?id=1326645 > This is the right behaviour and redhat will not fix this. > > So don't downgrade your features or you'll have to export-import all the > images. > I'm getting crazy. > > > > Il 23/06/2017 22:36, David Turner ha scritto: > > I upgraded to Jewel from Hammer and was able to enable those features on > all of my rbds that were format 2, which yours is. Just test it on some > non customer data and see how it goes. > > On Fri, Jun 23, 2017, 4:33 PM Massimiliano Cuttini <m...@phoenixweb.it> > wrote: > >> Ok, >> >> At moment my client use only nbd-rbd, can I use all these feature or this >> is something unavoidable? >> I guess it's ok. >> >> Reading around seems that a lost feature cannot be re-enabled due to >> back-compatibility with old clients. >> ... I guess I'll need to export and import in a new image fully feature. >> Is it? >> >> >> >> >> Il 23/06/2017 22:25, David Turner ha scritto: >> >> All of the features you are talking about likely require the >> exclusive-lock which requires the 4.9 linux kernel. You cannot map any >> RBDs that have these features enabled with any kernel older than that. >> >> The features you can enable are layering, exclusive-lock, object-map, and >> fast-diff. You cannot enable deep-flatten on any RBD ever. RBD's can only >> be created with that feature. You may need to enable these in a specific >> order. I believe that the order I have the features listed is the order >> you need to enable them in, at least that order should work. >> >> On Fri, Jun 23, 2017 at 3:41 PM Massimiliano Cuttini <m...@phoenixweb.it> >> wrote: >> >>> Hi everybody, >>> >>> I just realize that all my Images are completly without features: >>> >>> rbd info VHD-4c7ebb38-b081-48da-9b57-aac14bdf88c4 >>> rbd image 'VHD-4c7ebb38-b081-48da-9b57-aac14bdf88c4': >>> size 102400 MB in 51200 objects >>> order 21 (2048 kB objects) >>> block_name_prefix: rbd_data.5fde2ae8944a >>> format: 2 >>> features: >>> flags: >>> >>> try to enabling them will get this error: >>> >>> rbd: failed to update image features: (22) Invalid argument >>> 2017-06-23 21:20:03.748746 7fdec1b34d80 -1 librbd: cannot update immutable >>> features >>> >>> I read on the guide I shoulded had place in the config >>> rbd_default_features >>> >>> What can I do now to enable this feature all feature of jewel on all >>> images? >>> Can I insert all the feature of jewel or is there any issue with old >>> kernel? >>> >>> >>> Thanks, >>> Max >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@lists.ceph.com >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>> >> >> > > > _______________________________________________ > ceph-users mailing > listceph-us...@lists.ceph.comhttp://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
