Scrub behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello

I am experimenting with how Ceph (13.2.2) deals with on-disk data corruption, and I've run into some unexpected behavior. I am wondering if somebody could comment on whether I understand things correctly.

In my tests I would dd /dev/urandom onto an OSD's disk and see what would happen. I don't fill up the entire disk (that causes OSD to crash) and choose an OSD that is pretty full.

It looks like regular scrubs don't detect any problems at all, and I actually don't see any disk activity. So I guess only the stuff that is in memory is getting scrubbed?

When I initiate a deep scrub of an OSD, it looks like only PGs for which that OSD is the primary are checked. Is this correct? If so, how is corruption of other PGs on that OSD is detected?


Thanks,

Vlad
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux