Oh really, I thought it would be an error. My bad. There was an osd flag "full" which is not usable anymore, I never used it so I just tried it with full OSD which should lead to an error (and it does): host:~ # ceph -s cluster: id: 8f279f36-811c-3270-9f9d-58335b1bb9c0 health: HEALTH_ERR 1 full osd(s) 22 pool(s) full A created a pool with 1 pg and size 1, created an rbd image in that pool and filled that up until the respective OSD was full. I have a virtual lab cluster with 20GB OSDs so it didn't take that long. If you try this, make sure to disable pg-autoscaler on that pool or otherwise it will increase pg-num. Does that help? Regards, Eugen Zitat von George Shuklin <george.shuklin@gmail.com>:
But HEALTH_ERR is a bit more tricky. Any ideas?
I think if you set a very low quota for a pool (e.g. 1000 bytes or so) and fill it up it should create a HEALTH_ERR status, IIRC. Cool idea. Unfortunately, even with 1 byte quota (and some data in
On 21/01/2021 13:02, Eugen Block wrote: the pool), it's HEALTH_WARN, 1 pool(s) full _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io