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.corvotempe...@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@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users -- Dmitry Glushenok Jet Infosystems
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
