Gluster users - Jun 2016 - Bit rot disabled as default

2016-06-15 18:12 GMT+02:00 ??????? ???????? <glush at
jet.msk.su>:
> 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.
I think you are right
But what about sharding? In this case, the hash should be created for
each shard and not the whole file.

Sharding almost solves the problem (for inactive blocks), but it was considered
as stable just today :)

http://blog.gluster.org/2016/06/glusterfs-3-8-released/
<http://blog.gluster.org/2016/06/glusterfs-3-8-released/>
- Sharding is now stable for VM image storage.

--
Dmitry Glushenok
Jet Infosystems
> 15 ???? 2016 ?., ? 19:42, Gandalf Corvotempesta <gandalf.corvotempesta
at gmail.com> ???????(?):
> 
> 2016-06-15 18:12 GMT+02:00 ??????? ???????? <glush at jet.msk.su>:
>> 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.
> 
> I think you are right
> But what about sharding? In this case, the hash should be created for
> each shard and not the whole file.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160615/0b2e5fe6/attachment.html>