resulted in the correct op-version all around and about a
week free of these errors.
On 2018-03-01 12:38, Ryan Lee wrote:
Thanks for your response - is there more that would be useful in
addition to what I already attached? We're logging at default level on
the brick side and at error on cl
We've been on the Gluster 3.7 series for several years with things
pretty stable. Given that it's reached EOL, yesterday I upgraded to
3.13.2. Every Gluster mount and server was disabled then brought back
up after the upgrade, changing the op-version to 31302 and then trying
it all out.
It
