Perhaps for checksum verification and data integrity checks - continuously use this - https://github.com/avati/arequal
On Thu, Aug 29, 2013 at 8:32 AM, Michael Peek <[email protected]> wrote: > On 08/26/2013 01:14 PM, Anand Avati wrote: > > Michael, > > The problem looks very strange. We haven't come across such an issue > > (in glusterfs) so far. However I do recall seeing such bit flips at a > > customer site in the past, and in the end it was diagnosed to be a > > hardware issue. Can you retry a few runs of same rsync directly to the > > backends through nfs or rsyncd (without involving gluster or ssh), > > from the same client and same data set, to both the servers and see if > > you can reproduce such a md5sum/sha1sum mismatch? > > > > Will do. > > On 08/27/2013 03:41 AM, Giovanni Toraldo wrote: > > An overnight run of memtest86 on every node it's reasonable too. > > I am doing this now. (I should have thought about trying this before I > posted.) > > Michael Peek > _______________________________________________ > Gluster-users mailing list > [email protected] > http://supercolony.gluster.org/mailman/listinfo/gluster-users > -- *Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes*
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
