Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-27 Thread Steve Anthony
>> across this thread >> >> If your OSD is crashing and you are still running on a Luminous build that >> does not have the fix in the pull request below, you will >> need to compile the ceph-osd binary and replace it on the affected OSD node. >> This will get your

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-14 Thread Steve Anthony
gt; So I've recompiled a 12.2.5 ceph-osd binary with the fix included in > https://github.com/ceph/ceph/pull/22396 > > The OSD has restarted as expected and the PG is now active+clean > ..success so far. > > What's the best method to clean up the stray snapshot on OSD.46?

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-14 Thread Nick Fisk
] On Behalf Of Nick Fisk Sent: 07 June 2018 14:01 To: 'ceph-users' Subject: Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end()) So I've recompiled a 12.2.5 ceph-osd binary with the fix included in https://github.com/ceph/ceph/pull/22396 The OSD has restarted as expected and the PG

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-07 Thread Nick Fisk
-store-tool, but not sure if I want to clean the clone metadata or try and remove the actual snapshot object. -Original Message- From: ceph-users On Behalf Of Nick Fisk Sent: 05 June 2018 17:22 To: 'ceph-users' Subject: Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-05 Thread Sage Weil
On Tue, 5 Jun 2018, Paul Emmerich wrote: > 2018-06-05 17:42 GMT+02:00 Nick Fisk : > > > Hi, > > > > After a RBD snapshot was removed, I seem to be having OSD's assert when > > they try and recover pg 1.2ca. The issue seems to follow the > > PG around as OSD's fail. I've seen this bug tracker and

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-05 Thread Nick Fisk
uot; snapshot object and then allow thigs to backfill? -Original Message- From: ceph-users On Behalf Of Nick Fisk Sent: 05 June 2018 16:43 To: 'ceph-users' Subject: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end()) Hi, After a RBD snapshot was removed, I seem to be havi

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-05 Thread Nick Fisk
From: ceph-users On Behalf Of Paul Emmerich Sent: 05 June 2018 17:02 To: n...@fisk.me.uk Cc: ceph-users Subject: Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end()) 2018-06-05 17:42 GMT+02:00 Nick Fisk mailto:n...@fisk.me.uk> >: Hi, After a RBD sn

Re: [ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-05 Thread Paul Emmerich
2018-06-05 17:42 GMT+02:00 Nick Fisk : > Hi, > > After a RBD snapshot was removed, I seem to be having OSD's assert when > they try and recover pg 1.2ca. The issue seems to follow the > PG around as OSD's fail. I've seen this bug tracker and associated mailing > list post, but would appreciate if

[ceph-users] FAILED assert(p != recovery_info.ss.clone_snaps.end())

2018-06-05 Thread Nick Fisk
Hi, After a RBD snapshot was removed, I seem to be having OSD's assert when they try and recover pg 1.2ca. The issue seems to follow the PG around as OSD's fail. I've seen this bug tracker and associated mailing list post, but would appreciate if anyone can give any pointers.