What does "ceph osd pool ls detail" say? Respectfully, *Wes Dillingham* wes@xxxxxxxxxxxxxxxxx LinkedIn <http://www.linkedin.com/in/wesleydillingham> On Thu, May 26, 2022 at 11:24 AM Sarunas Burdulis < sarunas@xxxxxxxxxxxxxxxxxx> wrote: > Running > > `ceph osd ok-to-stop 0` > > shows: > > {"ok_to_stop":false,"osds":[1], > "num_ok_pgs":25,"num_not_ok_pgs":2, > "bad_become_inactive":["13.a","13.11"], > > "ok_become_degraded":["0.4","0.b","0.11","0.1a","0.1e","0.3c","2.5","2.10","3.19","3.1a","4.7","4.19","4.1e","6.10","12.1","12.6","15.9","21.17","21.18","36.8","36.13","41.7","41.1b","42.6","42.1a"]} > Error EBUSY: unsafe to stop osd(s) at this time (2 PGs are or would > become offline) > > What are “bad_become_inactive” PGs? > What can be done to make OSD into “ok-to-stop” (or override it)? > > `ceph -s` still reports HEALT_OK and all PGs active+clean. > > Upgrade to 16.2.8 still complains about non-stoppable OSDs and won't > proceed. > > -- > Sarunas Burdulis > Dartmouth Mathematics > math.dartmouth.edu/~sarunas > > · https://useplaintext.email · > _______________________________________________ > 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
 |