On 05/15/2018 12:38 PM, mabi wrote:
Dear all,
I have upgraded my replica 3 GlusterFS cluster (and clients) last Friday from
3.12.7 to 3.12.9 in order to fix this bug but unfortunately I notice that I
still have exactly the same problem as initially posted in this thread.
It looks like this bug is not resolved as I just got right now 3 unsynched
files on my arbiter node like I used to do before upgrading. This problem
started since I upgraded to 3.12.7...
Could you provide the stat and 'getfattr -d -m . - hex
brick/path/to/file' outputs of one of these files and also the
corresponding parent directory from all 3 bricks?
Thanks,
Ravi
Thank you very much in advance for your advise.
Best regards,
Mabi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On April 9, 2018 2:31 PM, Ravishankar N <ravishan...@redhat.com> wrote:
On 04/09/2018 05:54 PM, Dmitry Melekhov wrote:
09.04.2018 16:18, Ravishankar N пишет:
On 04/09/2018 05:40 PM, mabi wrote:
Again thanks that worked and I have now no more unsynched files.
You mentioned that this bug has been fixed in 3.13, would it be
possible to backport it to 3.12? I am asking because 3.13 is not a
long-term release and as such I would not like to have to upgrade to
3.13.
I don't think there will be another 3.12 release.
Why not? It is LTS, right?
My bad. Just checked the schedule [1], and you are right. It is LTM.
[1] https://www.gluster.org/release-schedule/
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
