It's not very intuitive or easy to look at right now (there are plans from the recent developer summit to improve things), but the central log should have output about exactly what objects are busted. You'll then want to compare the copies manually to determine which ones are good or bad, get the good copy on the primary (make sure you preserve xattrs), and run repair. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com
On Mon, Jul 7, 2014 at 6:48 PM, Randy Smith <rbsm...@adams.edu> wrote: > Greetings, > > I upgraded to firefly last week and I suddenly received this error: > > health HEALTH_ERR 1 pgs inconsistent; 1 scrub errors > > ceph health detail shows the following: > > HEALTH_ERR 1 pgs inconsistent; 1 scrub errors > pg 3.c6 is active+clean+inconsistent, acting [2,5] > 1 scrub errors > > The docs say that I can run `ceph pg repair 3.c6` to fix this. What I want > to know is what are the risks of data loss if I run that command in this > state and how can I mitigate them? > > -- > Randall Smith > Computing Services > Adams State University > http://www.adams.edu/ > 719-587-7741 > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
