Hi You can use the script available at https://github.com/TheJJ/ceph-balancer/blob/master/placementoptimizer.py to check the status of backfilling and PG state, and also to cancel backfilling using upmap. To view the movement status of all PGs in the backfilling state, you can execute the command "placementoptimizer.py showremapped" On Fri, Apr 14, 2023 at 11:20 AM Eugen Block <eblock@nde.ag> wrote:

Hi, your cluster is in backfilling state, maybe just wait for the backfill to finish? What is 'ceph -s' reporting? The PG could be backfilling to a different OSD as well. You could query the PG to see more details ('ceph pg 8.2a6 query'). By the way, the PGs you show are huge (around 174 GB with more than 200k objects), depending on the disks you use a split could help gain more performance (if that is an issue for you).

Regards, Eugen

Zitat von xadhoom76@gmail.com:

...

Hi to all Using ceph 17.2.5 i have 3 pgs in stuck state

ceph pg map 8.2a6 osdmap e32862 pg 8.2a6 (8.2a6) -> up [88,100,59] acting [59,100] looking at it ho 88 ,100 and 59 i got that

ceph pg ls-by-osd osd.100 | grep 8.2a6 8.2a6 211004 209089 0 0 174797925205 0 0 7075 active+undersized+degraded+remapped+backfilling 21m 32862'1540291 32862:3387785 [88,100,59]p88 [59,100]p59 2023-03-12T08:08:00.903727+0000 2023-03-12T08:08:00.903727+0000 6839 queued for deep scrub

ceph pg ls-by-osd osd.59 | grep 8.2a6 8.2a6 211005 209084 0 0 174798941087 0 0 7076 active+undersized+degraded+remapped+backfilling 22m 32862'1540292 32862:3387798 [88,100,59]p88 [59,100]p59 2023-03-12T08:08:00.903727+0000 2023-03-12T08:08:00.903727+0000 6839 queued for deep scrub

BUT ceph pg ls-by-osd osd.88 | grep 8.2a6 ---> NONE

it is missing .... how to proceed ? Best regards _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io

_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io

I didn't mean you should split your PGs now, that won't help because there is already backfilling going on. I would revert the pg_num changes (since nothing actually happened yet there's no big risk) and wait for the backfill to finish. You don't seem to have inactive PGs so it shouldn't be an issue as long as nothing else breaks down. Do you see progress of the backfilling? Do the numbers of misplaced objects change? Zitat von xadhoom76@gmail.com:

Thanks, I try to change the pg and pgp number to an higher value but pg do not increase.... ta: pools: 8 pools, 1085 pgs objects: 242.28M objects, 177 TiB usage: 553 TiB used, 521 TiB / 1.0 PiB avail pgs: 635281/726849381 objects degraded (0.087%) 91498351/726849381 objects misplaced (12.588%) 773 active+clean 288 active+remapped+backfilling 11 active+clean+scrubbing+deep 10 active+clean+scrubbing 3 active+undersized+degraded+remapped+backfilling

still have those 3 pg in stuck _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io

Hi, the system is still in backfilling and still have the same pg in degraded. I see that % of degraded object is in still. I mean it never decrease belove 0.010% from days. Is the backfilling connected to the degraded ? System must finish backfilling before finishing the degraded one ? [WRN] PG_DEGRADED: Degraded data redundancy: 84469/826401567 objects degraded (0.010%), 1 pg degraded, 1 pg undersized pg 8.283 is stuck undersized for 92m, current state active+undersized+degraded+remapped+backfilling, last acting [17,59] And stopping the scrub lead to inconsistent pgs..... Thanks for any help.