BitRot or Data Rot is when file or object sits un-disturb on the disk or unaccess from day by day or month by month or year by year and when you go to your pen drive, hard disk or take out your DVD and you see that you can't access that data because bit have flipped called as BitRot or DataRot.
BitRot detection is a technique used to identify certain insidious
type of disk errors where data is silently corrupted with no
indication from the disk to the storage software layer that an error
has occurred.
With GlusterFS 3.7, its possible to detect corruption caused due to
bitrot and take steps to rectify them. When bitrot detection is
enabled on a Gluster volume, files are signed after they have been
written. A periodic filesystem scrubber verifies the integrity of
signed files are flags (or marks) files which have mismatching
signature. Corrupted files are typically denied access to clients
unless it's a replicated volume where it's still possible to access
the "good" copy and repair the corrupted file.
2. We are, Gluster developers at Red Hat
... participate in meetups, open source events
... hang out on #freenode: gluster, gluster-dev
nick: overclk, ggarg
... interact with community: gluster-devel@gluster.org
gluster-users@gluster.org
17. Implementation
Details (cotd..)
Object versioning
Versioned upon modification
Versioning xattr (64 bit)
Reflect object state
Signature
xattr
Attached to a version
22. 3.7
Bitrot detection
No recovery
In comes sharding
3.7.2
Recovery support
3.7.4
Bug fixes
Scrub status
3.8
Sharding ready
Bitrot adaption
4.0
Hell of a change
Sharding by default
Checksum everything