Le 20/09/2024 à 11:01:20+0200, Albert Shih a écrit Hi, > > > > > > Is they are any way to find which pg ceph status are talking about. > > > > 'ceph health detail' will show you which PG it's warning about. > > Too easy for me ;-) ;-)...Thanks ;-) > > > > > > Is they are any way to see the progress or scrubbing/remapping/backfill ? > > > > You can see when (deep-)scrubs have been started in the OSD logs or > > depending on your cluster log configuration: > > > > ceph log last 1000 debug cluster | grep scrub > > Thanks. > > So I think I get some issue with one osd > > 2024-09-20T08:55:59.760766+0000 osd.356 (osd.356) 84 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:03.751487+0000 osd.356 (osd.356) 85 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:05.742816+0000 osd.356 (osd.356) 86 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:07.822277+0000 osd.356 (osd.356) 87 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:08.795748+0000 osd.356 (osd.356) 88 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:09.749838+0000 osd.356 (osd.356) 89 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:10.778235+0000 osd.356 (osd.356) 90 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:14.792102+0000 osd.356 (osd.356) 91 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:15.832620+0000 osd.356 (osd.356) 92 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:16.791811+0000 osd.356 (osd.356) 93 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:17.798181+0000 osd.356 (osd.356) 94 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:19.793526+0000 osd.356 (osd.356) 95 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:20.809140+0000 osd.356 (osd.356) 96 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:21.835052+0000 osd.356 (osd.356) 97 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:22.817378+0000 osd.356 (osd.356) 98 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:28.887092+0000 osd.356 (osd.356) 99 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:32.907468+0000 osd.356 (osd.356) 100 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:33.900065+0000 osd.356 (osd.356) 101 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:37.853769+0000 osd.356 (osd.356) 102 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:38.850513+0000 osd.356 (osd.356) 103 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:46.799896+0000 osd.356 (osd.356) 104 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:50.915450+0000 osd.356 (osd.356) 105 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:53.875875+0000 osd.356 (osd.356) 106 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:55.791675+0000 osd.356 (osd.356) 107 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:57.833012+0000 osd.356 (osd.356) 108 : cluster [DBG] 4.51 deep-scrub starts > 2024-09-20T08:56:59.818262+0000 osd.356 (osd.356) 109 : cluster [DBG] 4.51 deep-scrub starts > > but the osd are still in > > queued for deep scrub Yeah...well after few hours the scrub eventually started. So eveything seem fine. Regards -- Albert SHIH 🦫 🐸 Observatoire de Paris France Heure locale/Local time: ven. 20 sept. 2024 14:13:20 CEST _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |