Incomplete pg , any chance to to make it survive or data loss :( ?
Hi, What can I do with this pg to make it work? We lost and don't have the osds 61,122 but we have the 32,33,70. I've exported the pg chunk from them, but they are very small and when I imported back to another osd that osd never started again so I had to remove that chunk (44.1aas2, 44.1aas3) to be able to start the osd. [WRN] PG_AVAILABILITY: Reduced data availability: 1 pg incomplete pg 44.1aa is incomplete, acting [59,128,127,43] (reducing pool cephfs1-data01-pool min_size from 3 may help; search ceph.com/docs for 'incomplete') [WRN] PG_NOT_DEEP_SCRUBBED: 1 pgs not deep-scrubbed in time pg 44.1aa not deep-scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] PG_NOT_SCRUBBED: 1 pgs not scrubbed in time pg 44.1aa not scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] SLOW_OPS: 96 slow ops, oldest one blocked for 228287 sec, osd.59 has slow ops This is the pg query and pg map important parts: "probing_osds": [ "29(3)", "34(3)", "43(3)", "56(1)", "59(0)", "72(2)", "73(2)", "74(2)", "127(2)", "128(1)", "131(2)" ], "down_osds_we_would_probe": [ 32, 33, 61, 70, 122 ], "peering_blocked_by": [], "peering_blocked_by_detail": [ { "detail": "peering_blocked_by_history_les_bound" osdmap e5666778 pg 44.1aa (44.1aa) -> up [59,128,127,43] acting [59,128,127,43] Internal ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.
Forgot to say, this is an octopus 15.2.9 cluster, there isn't any force_create_pg option that has couple of thread to make it work. https://tracker.ceph.com/issues/10411 https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c... [https://www.oreilly.com/library/cover/9781788397605/]<https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c67-10aa-4cf2-8812-e38c861cdc5d.xhtml> Stuck inactive incomplete PGs in Ceph - Mastering Proxmox - Third Edition [Book] - O'Reilly Media<https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c67-10aa-4cf2-8812-e38c861cdc5d.xhtml> Stuck inactive incomplete PGs in Ceph If any PG is stuck due to OSD or node failure and becomes unhealthy, resulting in the cluster becoming inaccessible due to a blocked … - Selection from Mastering Proxmox - Third Edition [Book] www.oreilly.com Bug #10411: PG stuck incomplete after failed node - Ceph - Ceph<https://tracker.ceph.com/issues/10411> Yesterday, I was in the process of expanding the number of PGs in one of our pools. While I was doing this, one of the disks in an OSD failed (probably due to the high load of the cluster at that point). tracker.ceph.com ________________________________ From: Szabo, Istvan (Agoda) <Istvan.Szabo@agoda.com> Sent: Monday, March 22, 2021 2:33 PM To: Ceph Users <ceph-users@ceph.io> Subject: [ceph-users] Incomplete pg , any chance to to make it survive or data loss :( ? Hi, What can I do with this pg to make it work? We lost and don't have the osds 61,122 but we have the 32,33,70. I've exported the pg chunk from them, but they are very small and when I imported back to another osd that osd never started again so I had to remove that chunk (44.1aas2, 44.1aas3) to be able to start the osd. [WRN] PG_AVAILABILITY: Reduced data availability: 1 pg incomplete pg 44.1aa is incomplete, acting [59,128,127,43] (reducing pool cephfs1-data01-pool min_size from 3 may help; search ceph.com/docs for 'incomplete') [WRN] PG_NOT_DEEP_SCRUBBED: 1 pgs not deep-scrubbed in time pg 44.1aa not deep-scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] PG_NOT_SCRUBBED: 1 pgs not scrubbed in time pg 44.1aa not scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] SLOW_OPS: 96 slow ops, oldest one blocked for 228287 sec, osd.59 has slow ops This is the pg query and pg map important parts: "probing_osds": [ "29(3)", "34(3)", "43(3)", "56(1)", "59(0)", "72(2)", "73(2)", "74(2)", "127(2)", "128(1)", "131(2)" ], "down_osds_we_would_probe": [ 32, 33, 61, 70, 122 ], "peering_blocked_by": [], "peering_blocked_by_detail": [ { "detail": "peering_blocked_by_history_les_bound" osdmap e5666778 pg 44.1aa (44.1aa) -> up [59,128,127,43] acting [59,128,127,43] Internal ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io Internal Internal
Some news, due to the ceph pg inactive list command gave back that 0 objects are in this pg, I've marked complete on the primary osd, now it is unfound. Now I've stucked again 😕 [WRN] OBJECT_UNFOUND: 4/58369044 objects unfound (0.000%) pg 44.1aa has 4 unfound objects [ERR] PG_DAMAGED: Possible data damage: 1 pg recovery_unfound pg 44.1aa is active+recovery_unfound+undersized+degraded+remapped, acting [59,2147483647,127,43], 4 unfound [WRN] PG_DEGRADED: Degraded data redundancy: 4/232017450 objects degraded (0.000%), 1 pg degraded, 1 pg undersized pg 44.1aa is stuck undersized for 6m, current state active+recovery_unfound+undersized+degraded+remapped, last acting [59,2147483647,127,43] [WRN] PG_NOT_DEEP_SCRUBBED: 1 pgs not deep-scrubbed in time pg 44.1aa not deep-scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] PG_NOT_SCRUBBED: 1 pgs not scrubbed in time pg 44.1aa not scrubbed since 2021-01-14T05:50:23.852626+0100 ________________________________ From: Szabo, Istvan (Agoda) <Istvan.Szabo@agoda.com> Sent: Monday, March 22, 2021 3:00 PM To: Ceph Users <ceph-users@ceph.io> Subject: [ceph-users] Re: Incomplete pg , any chance to to make it survive or data loss :( ? Forgot to say, this is an octopus 15.2.9 cluster, there isn't any force_create_pg option that has couple of thread to make it work. https://tracker.ceph.com/issues/10411 https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c... [https://www.oreilly.com/library/cover/9781788397605/]<https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c67-10aa-4cf2-8812-e38c861cdc5d.xhtml> Stuck inactive incomplete PGs in Ceph - Mastering Proxmox - Third Edition [Book] - O'Reilly Media<https://www.oreilly.com/library/view/mastering-proxmox-/9781788397605/42d80c67-10aa-4cf2-8812-e38c861cdc5d.xhtml> Stuck inactive incomplete PGs in Ceph If any PG is stuck due to OSD or node failure and becomes unhealthy, resulting in the cluster becoming inaccessible due to a blocked … - Selection from Mastering Proxmox - Third Edition [Book] www.oreilly.com<http://www.oreilly.com> Bug #10411: PG stuck incomplete after failed node - Ceph - Ceph<https://tracker.ceph.com/issues/10411> Yesterday, I was in the process of expanding the number of PGs in one of our pools. While I was doing this, one of the disks in an OSD failed (probably due to the high load of the cluster at that point). tracker.ceph.com ________________________________ From: Szabo, Istvan (Agoda) <Istvan.Szabo@agoda.com> Sent: Monday, March 22, 2021 2:33 PM To: Ceph Users <ceph-users@ceph.io> Subject: [ceph-users] Incomplete pg , any chance to to make it survive or data loss :( ? Hi, What can I do with this pg to make it work? We lost and don't have the osds 61,122 but we have the 32,33,70. I've exported the pg chunk from them, but they are very small and when I imported back to another osd that osd never started again so I had to remove that chunk (44.1aas2, 44.1aas3) to be able to start the osd. [WRN] PG_AVAILABILITY: Reduced data availability: 1 pg incomplete pg 44.1aa is incomplete, acting [59,128,127,43] (reducing pool cephfs1-data01-pool min_size from 3 may help; search ceph.com/docs for 'incomplete') [WRN] PG_NOT_DEEP_SCRUBBED: 1 pgs not deep-scrubbed in time pg 44.1aa not deep-scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] PG_NOT_SCRUBBED: 1 pgs not scrubbed in time pg 44.1aa not scrubbed since 2021-01-14T05:50:23.852626+0100 [WRN] SLOW_OPS: 96 slow ops, oldest one blocked for 228287 sec, osd.59 has slow ops This is the pg query and pg map important parts: "probing_osds": [ "29(3)", "34(3)", "43(3)", "56(1)", "59(0)", "72(2)", "73(2)", "74(2)", "127(2)", "128(1)", "131(2)" ], "down_osds_we_would_probe": [ 32, 33, 61, 70, 122 ], "peering_blocked_by": [], "peering_blocked_by_detail": [ { "detail": "peering_blocked_by_history_les_bound" osdmap e5666778 pg 44.1aa (44.1aa) -> up [59,128,127,43] acting [59,128,127,43] Internal ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io Internal Internal _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io Internal Internal
participants (1)
-
Szabo, Istvan (Agoda)