Hi,
After Nautilus there were two omap usage stats upgrades:
Octopus (v15) fsck (on by default) enables per-pool omap usage stats.
Pacific (v16) fsck (off by default) enables per-pg omap usage stats.
(fsck is off by default in pacific because it takes quite some time to
update the on-disk metadata, and btw the pacific fsck had a data
corrupting bug until 16.2.7 [1]).
You're getting a warning because you skipped over Octopus (which is
ok!) but this jump means you miss the per-pool omap stats upgrade.
Confusingly, the per-pool omap warning is *on* by default, hence the
warning message.
You can disable the per-pool warning with:
ceph config set global bluestore_warn_on_no_per_pool_omap false
Or you can decide to fsck the OSDs now with 16.2.7. This will add
per-pg omap stats and clear the warning.
This is documented here:
https://docs.ceph.com/en/latest/rados/operations/health-checks/#bluestore-no-per-pool-omap
Cheers, Dan
On Thu, Mar 10, 2022 at 12:43 PM Claas Goltz <claas.goltz@xxxxxxxxx> wrote:
>
> Hi,
>
> I’m in the process of upgrading all our ceph servers from 14.2.9 to 16.2.7.
>
> Two of three monitors are on 16.2.6 and one is 16.2.7. I will update them
> soon.
>
>
>
> Before updating to 16.2.6/7 I set the “bluestore_fsck_quick_fix_on_mount
> false” flag and I already upgraded more than the half of my OSD Hosts (10
> so far) to the latest Version without any problems. My Health Check now
> says:
>
> “92 OSD(s) reporting legacy (not per-pool) BlueStore omap usage stats”
>
>
>
> How should I handle the warning now?
>
> Thanks!
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
