Yes Greg, agreed, I found some corruption during BlueFS replay , could also be caught in detail if I run fsck() may be.. Will do it , but, in dev environment time consumed during fsck() could be a challenge (though I have no idea how long it will take per TB of data, never ran it) considering the number of time we need to restart OSDs.. Thanks & Regards Somnath -----Original Message----- From: Gregory Farnum [mailto:gfarnum@xxxxxxxxxx] Sent: Wednesday, August 03, 2016 4:03 PM To: Somnath Roy Cc: Stillwell, Bryan J; ceph-users@xxxxxxxxxxxxxx Subject: Re: Multi-device BlueStore OSDs multiple fsck failures On Wed, Aug 3, 2016 at 3:50 PM, Somnath Roy <Somnath.Roy@xxxxxxxxxxx> wrote: > Probably, it is better to move to latest master and reproduce this defect. Lot of stuff has changed between this. > This is a good test case and I doubt any of us testing by enabling fsck() on mount/unmount. Given that the allocator keeps changing, running fsck frequently while testing is probably a good idea... ;) PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies). _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |