Are you sure the osd begin to scrub? maybe you could check it from osd log, or using 'ceph pg dump' to check whether the scrub stamp changes or not. Because there is some strategy which would reject the scrub command Such as the system load , osd_scrub_min_interval, osd_deep_scrub_interval and so on 2015-10-28 17:39 GMT+08:00 changtao381 <changtao381@xxxxxxx>: > Hi, > > I’m testing the deep-scrub function of ceph. And the test steps are below : > > 1) I put an object on ceph using command : > rados put test.txt test.txt –p testpool > > The size of testpool is 3, so there three replicates on three osds: > > osd.0: /data1/ceph_data/osd.0/current/1.0_head/test.txt__head_8B0B6108__1 > osd.1: /data2/ceph_data/osd.1/current/1.0_head/test.txt__head_8B0B6108__1 > osd.2 /data3/ceph_data/osd.2/current/1.0_head/test.txt__head_8B0B6108__1 > > 2) I modified the content of one replica on osd.0 using vim editor directly on disk > > 3) I run the command > ceph pg deep-scrub 1.0 > > and expect it can check the inconsistent error out, but it fails. It doesn’t find the error > why? > > Any suggestions will be appreciated! Thanks > > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, xinze -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
