Hello again, Just an update on this; I restarted all the acting osd daemons, and the unfound message is now gone. There must have been some sort of a book keeping error which got fixed on daemon restart. -----Original Message----- From: Eino Tuominen Sent: 4. toukokuuta 2015 13:27 To: Eino Tuominen; ceph-users@xxxxxxxx Subject: RE: A pesky unfound object Hi everybody, Does anybody have any clue on this? I've run a deep scrub on the pg and the status is still showing one unfound object. This is a test cluster only, but I'd like to learn what has happened and why... Thanks, -- Eino Tuominen -----Original Message----- From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] On Behalf Of Eino Tuominen Sent: 29. huhtikuuta 2015 15:10 To: ceph-users@xxxxxxxx Subject: A pesky unfound object Hello, A routine reboot of one of the osd servers resulted in one unfound object. Following the documentation on unfound objects I have run ceph pg 5.306 mark_unfound_lost delete But, I've still got: # ceph health detail HEALTH_WARN recovery 1/2661869 unfound (0.000%) recovery 1/2661869 unfound (0.000%) This is our test cluster running Giant 0.87.1. What has happened and how can I resolve this? -- Eino Tuominen _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |