[Gluster-devel] Need help with bitrot

Joseph Fernandes josferna at redhat.com
Fri Feb 26 01:35:35 UTC 2016

Hope this helps

Courtesy : Raghvendra Talur (rtalur at redhat.com)

1. Clone glusterfs repo to your laptop and get acquainted with dev workflow.

2. If you find using your laptop as the test machine for Gluster as too
scary, here is a vagrant based mechanism to get VMs setup on your laptop
easily for Gluster testing.

3.Find my Gluster Introduction blog post here in the preview link:


4. Follow all the lessons here in Translator 101 series for build on your
understanding of Gluster.

5. Try to fix or understand any of the bugs in this list


----- Original Message -----
From: "Ajil Abraham" <ajil95.abraham at gmail.com>
To: "FNU Raghavendra Manjunath" <rabhat at redhat.com>
Cc: "Gluster Devel" <gluster-devel at gluster.org>
Sent: Thursday, February 25, 2016 8:58:35 PM
Subject: Re: [Gluster-devel] Need help with bitrot

Thanks FNU Raghavendra. Does the signing happen only when the file data changes or even when extended attribute changes? 

I am also trying to understand the Gluster internal data structures. Are there any materials for the same? Similarly for the translators, the way they are stacked on client & server side, how control flows between them. Can somebody please help? 

- Ajil 

On Thu, Feb 25, 2016 at 7:27 AM, FNU Raghavendra Manjunath < rabhat at redhat.com > wrote: 

Hi Ajil, 

Expiry policy tells the signer (Bit-rot Daemon) to wait for a specific period of time before signing a object. 

Whenever a object is modified, a notification is sent to the signer by brick process (bit-rot-stub xlator sitting in the I/O path) upon getting a release (i.e. when all the fds of that object are closed). The expiry policy tells the signer to wait for some time (by default its 120 seconds) before signing that object. It is done because, suppose the signer starts signing (i.e. read the object + calculate the checksum + store the checksum) a object the object gets modified again, then a new notification has to be sent and again signer has to sign the object by calculating the checksum. Whereas if the signer waits for some time and receives a new notification on the same object when its waiting, then it can avoid signing for the first notification. 

Venky, do you want to add anything more? 


On Wed, Feb 24, 2016 at 12:28 AM, Ajil Abraham < ajil95.abraham at gmail.com > wrote: 


I am a student interested in GlusterFS. Trying to understand the design of GlusterFS. Came across the Bitrot design document in Google. There is a mention of expiry policy used to sign the files. I did not clearly understand what the expiry policy is. Can somebody please help? 


Gluster-devel mailing list 
Gluster-devel at gluster.org 

Gluster-devel mailing list
Gluster-devel at gluster.org

More information about the Gluster-devel mailing list