> > Am 14.05.2013 02:11, schrieb James Harper: > >> > >> Am 14.05.2013 01:46, schrieb James Harper: > >>> After replacing a failed harddisk, ceph health reports "HEALTH_ERR 14 > pgs > >> inconsistent; 18 scrub errors" > >>> > >>> The disk was a total loss so I replaced it, ran mkfs etc and rebuilt the osd > >> and while it has resynchronised everything the above still remains. > >>> > >>> What should I do to resolve this? > >> > >> have you tried to repair the pgs? > >> > >> you can do ceph health details and then run ceph pg repair <pg> to repair > the > >> inconsistent PGs > >> > > > > I didn't know how to proceed so I hadn't done anything. I have issues the > repair commands now and they are coming good. > > > > Does this mean I have lost data somewhere? If not, why isn't the repair > automatic? > > > > No the data should be safe if the repair succeeds. > Thanks. The repair has now completed so I'm all healthy again (or at least I would be if one of my mon's wasn't running low on disk!) I'll run a bunch of tests to confirm the state of the data. I'm still in the testing phase with ceph so I don't have any data of consequence on there, just a domain controller (one of several so lots of redundancy) which had gone BSoD at some point while things were failing, but has booted up again since and appears to be working. I'm still seeing this on the client in the logs every 25 minutes or so though: May 14 10:11:23 bitvs5 kernel: [947275.120247] libceph: osd82 192.168.200.191:6882 socket closed May 14 10:11:23 bitvs5 kernel: [947275.121654] libceph: osd82 192.168.200.191:6882 connect authorization failure Which appears to have been happening since I rebuilt the osd. Have I missed copying a key somewhere? Client is Debian "wheezy" with 3.2.x kernel, using the kernel client. Could it just be that this is old? Thanks again! James _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |