> Please refer to Bitrot Feature:> http://www.gluster.org/community/documentation/index.php/Features/BitRot> I suppose it is already quite mature because it was already listed as a> feature on RedHat Gluster Storage 3.2 Administration Guide.If you are only looking for *detection*, it sounds like it is mature and working. If you want automatic *correction* on a replicated volume (like you find in ZFS or BTRFS), that doesn't appear to exist yet. I can't find an RHGS 3.2 admin guide, but I can find an RHGS 3.1 guide at https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Detecting_Data_Corruption.html and it matches the information on the gluster.org BitRot Feature page. They both say that automatic healing/correction is not available yet. The Features page says it is not in scope for Gluster 3.7 But detection is still a valuable feature. I'm sure correction will likely appear some time in the near future.
On 04/13/2016 01:41 PM, Alan Millar wrote:>> Please refer to Bitrot Feature: > >> http://www.gluster.org/community/documentation/index.php/Features/BitRot > >> I suppose it is already quite mature because it was already listed as a > >> feature on RedHat Gluster Storage 3.2 Administration Guide. > > If you are only looking for *detection*, it sounds like it is mature and working. If you want automatic *correction* on a replicated volume (like you find in ZFS or BTRFS), that doesn't appear to exist yet. > > > I can't find an RHGS 3.2 admin guide, but I can find an RHGS 3.1 guide at >RHGS 3.2 hasn't been released yet. RHGS 3.1.2 is the current version. -- Kaleb