# ceph --version
ceph version 10.2.5 (c461ee19ecbc0c5c330aca20f7392c9a00730367)
# ceph -s
cluster 7294caf5-c5f7-46dc-b9a7-84eea8d6b12c
health HEALTH_OK
monmap e1: 3 mons at {mon0-225-20=172.16.225.20:6789/0,mon1-225-21=172.16.225.21:6789/0,mon2-225-22=172.16.225.22:6789/0}
election epoch 112, quorum 0,1,2 mon0-225-20,mon1-225-21,mon2-225-22
fsmap e100: 1/1/1 up {0=mds-225-26=up:active}
osdmap e2864: 15 osds: 15 up, 15 in
flags sortbitwise,require_jewel_osds
pgmap v10468092: 648 pgs, 6 pools, 1437 GB data, 281 kobjects
2877 GB used, 90760 GB / 93637 GB avail
648 active+clean
client io 5321 B/s rd, 1378 kB/s wr, 1 op/s rd, 169 op/s wr
After upgrading to Ceph Jewel release, users should set the ¡®sortbitwise¡¯ flag to enable the new internal object sort order.
¡°sortbitwise¡± is a change in the internal sorting algorithm.
It is exposed to end-user only because of legacy (pre- jewel) compatibility.
Latest Ceph installation it should always be ¡®on¡¯
$ ceph osd set sortbitwise // To set the sortbitwise
$ ceph osd unset sortbitwise // to unset the sortbitwise