> Sure, there could be a custom 3.4.2 build on which they can continue to > operate till the problem gets fixed and tested thoroughly in 3.4.3. As I > mentioned in my OP, the current fix causes self-healing of symbolic links > to fail and this can potentially cause data loss. This has far more serious > consequences than a particular workload failing through libgfapi. > > We have delayed 3.4.2 by a fair while and I don't think we can afford to > hold it back further. We can consider releasing 3.4.3 soon after the errno > issue gets fixed properly and we have adequate test coverage on that. For > now the only option is to revert this patch. > > Fair enough, i will communicate this with them - will keep a custom build with 3.4.2 :-)
Thanks -- *Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes*
_______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
