Why not automate this or adding a command that does heal automatically when corruption is found?
Nobody wants corrupted files on the storage, why you don't heal automatically? Something like gluster volume bitrot *VOLNAME* heal start Il 1 mar 2017 7:32 AM, "Sweta Anandpara" <[email protected]> ha scritto: > Bitrot has a scrub process which detects the corrupted file. Once > detected, it is the prerogative of the user to follow the sequence of steps > [1] to trigger a heal. Having said that, client access to that file is not > impacted as it continues to serve data from the good copy. > Steps remain the same irrespective of a replica 2 or replica 3 volume. > > [1] https://access.redhat.com/documentation/en-US/Red_Hat_Storag > e/3.1/html/Administration_Guide/ch20s03.html > > Thanks, > Sweta > > On 02/28/2017 06:28 PM, Gandalf Corvotempesta wrote: > >> In a replica 3, what happens in case of bit-rot detection on a file ? >> Is gluster smart enough to detect this and automatically heal the >> corrupted files from other replicas ? >> What if in case of replica 2 ? How do know know which is right, >> server1 or server2, without a quorum ? >> >> What if the underling FS (like ZFS) is retuning an error in case of >> bit-rot ? ZFS should return an error if file is corrupted (and has not >> RAID to recover from), thus gluster should see the file as >> missing/corrupted and automatically trigger selfheal from other >> replicas ? >> _______________________________________________ >> Gluster-users mailing list >> [email protected] >> http://lists.gluster.org/mailman/listinfo/gluster-users >> > >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
