Gluster users - Jun 2016 - Bit rot disabled as default

I was looking at docs.
why bit rot protection is disabled by defaults?
with huge files like a qcow image a bit rot could lead to the whole image
corrupted and replicated to the whole cluster

Any drawbacks with bit rot detection to explain the default to off?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160615/4f785b99/attachment.html>

Hello.

May be because of current implementation of rotten bits detection - one hash for
whole file. Imagine 40 GB VM image - few parts of the image are modified
continuously (VM log files and application data are constantly changing). Those
writes making checksum invalid and BitD has to recalculate it endlessly. As the
result - checksum of VM image can never be verified.
> 15 ???? 2016 ?., ? 9:37, Gandalf Corvotempesta <gandalf.corvotempesta at
gmail.com> ???????(?):
> 
> I was looking at docs.
> why bit rot protection is disabled by defaults?
> with huge files like a qcow image a bit rot could lead to the whole image
corrupted and replicated to the whole cluster
> 
> Any drawbacks with bit rot detection to explain the default to off?
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
--
Dmitry Glushenok
Jet Infosystems

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160615/42d83f06/attachment.html>