Hi Karthik, thanks for the information. Xavi On 16/06/17 13:25, Karthik Subrahmanya wrote:
Hi Xavi, In my opinion it can not be called as a bug, it is kind of an improvement to the read-only and WORM translators. The solution to this is to identify the internal FOPs and allowing them to pass, even the read-only or WORM options are enabled. The patch [1] from Kotresh resolves this issue, which is currently under review. [1] https://review.gluster.org/#/c/16855/ Regards, Karthik On Fri, Jun 16, 2017 at 4:26 PM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx <mailto:pkarampu@xxxxxxxxxx>> wrote: I remember either Kotresh/Karthik recently sent patches to do something similar. Adding them to check if the know something about this On Fri, Jun 16, 2017 at 1:25 PM, Xavier Hernandez <xhernandez@xxxxxxxxxx <mailto:xhernandez@xxxxxxxxxx>> wrote: Hi, currently it seems that a read-only replica 2 volume cannot be healed because all attempts to make changes by the self-heal daemon on the damaged brick will fail with EROFS. It's true that no regular writes are allowed, so there's no possibility to cause damage by partial writes or similar things. However a read-only brick can still fail because of disk errors and some files could get corrupted or the entire disk will need to be replaced. Is this a bug or the only way to solve this problem is to make the volume read-write until self-heal finishes ? Thanks, Xavi _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> http://lists.gluster.org/mailman/listinfo/gluster-devel <http://lists.gluster.org/mailman/listinfo/gluster-devel> -- Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
