On 1 March 2017 at 17:15, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:
> 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?
>
Probably because
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"
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
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
