[Gluster-users] Upgrade from 6.9 to 7.7 stuck (peer is rejected)
hunter86_bg at yahoo.com
Sun Sep 6 19:44:32 UTC 2020
Your e-mail got in the spam...
If you haven't fixed the issue, check Hari's topic about quota issues (based on the error message you provided) : https://medium.com/@harigowtham/glusterfs-quota-fix-accounting-840df33fcd3a
Most probably there is a quota issue and you need to fix it.
В неделя, 23 август 2020 г., 11:05:27 Гринуич+3, mabi <mabi at protonmail.ch> написа:
So to be precise I am exactly having the following issue:
I could not wait any longer to find some workarounds or quick fixes so I decided to downgrade my rejected from 7.7 back to 6.9 which worked.
I would be really glad if someone could fix this issue or provide me a workaround which works because version 6 of GlusterFS is not supported anymore so I would really like to move on to the stable version 7.
Thank you very much in advance.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, August 22, 2020 7:53 PM, mabi <mabi at protonmail.ch> wrote:
> I just started an upgrade of my 3 nodes replica (incl arbiter) of GlusterFS from 6.9 to 7.7 but unfortunately after upgrading the first node, that node gets rejected due to the following error:
> [2020-08-22 17:43:00.240990] E [MSGID: 106012] [glusterd-utils.c:3537:glusterd_compare_friend_volume] 0-management: Cksums of quota configuration of volume myvolume differ. local cksum = 3013120651, remote cksum = 0 on peer myfirstnode.domain.tld
> So glusterd process is running but not glusterfsd.
> I am exactly in the same issue as described here:
> But I do not see any solutions or workaround. So now I am stuck with a degraded GlusterFS cluster.
> Could someone please advise me as soon as possible on what I should do? Is there maybe any workarounds?
> Thank you very much in advance for your response.
> Best regards,
Community Meeting Calendar:
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Gluster-users mailing list
Gluster-users at gluster.org
More information about the Gluster-users