Re: [Gluster-users] [SPAM] ACL issue v6.6, v6.7, v7.1, v7.2
Hey, I hit this bug, too. With disastrous results. I second this post. On 06.02.2020 19:59, Strahil Nikolov wrote: Hello List, Recently I had upgraded my oVirt + Gluster (v6.5 -> v6.6) and I hit an ACL bug , which forced me to upgrade to v7.0 Another oVirt user also hit the bug when upgrading to v6.7 and he had to rebuild his gluster cluster. Sadly, the fun doesn't stop here. Last week I have tried upgrading to v7.2 and again the ACL bug hit me. Downgrading to v7.1 doesn't help - so I downgraded to 7.0 and everything is operational. The bug report for the last issue: https://bugzilla.redhat.com/show_bug.cgi?id=1797099 I have 2 questions : 1. What is gluster's ACL evaluating/checking ? Is there an option to force gluster not to support ACL at all ? 2. Are you aware of the issue? That bug was supposed to be fixed a long time ago, yet the facts speak different. Thanks for reading this long post. Best Regards, Strahil Nikolov Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users -- Christian Reiss - em...@christian-reiss.de /"\ ASCII Ribbon christ...@reiss.nrw \ /Campaign X against HTML XMPP ch...@alpha-labs.net / \ in eMails WEB christian-reiss.de, reiss.nrw GPG Retrieval http://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost. Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Healing entries get healed but there are constantly new entries appearing
Hi Ulrich, >From the problem statement, seems like the client(s) have lost connection with brick. Can you give the following information? - How many clients are there for this volume and which version they are in? - gluster volume info & gluster volume status outputs - Check whether all the clients are connected to all the bricks. If you are using the fuse clients give the output of the following from all the clients cat /.meta/graphs/active/-client-*/private | egrep -i 'connected' -If you are using non fuse clients generate the statedumps ( https://docs.gluster.org/en/latest/Troubleshooting/statedump/) of each clients and give the output of grep -A 2 "xlator.protocol.client" /var/run/gluster/ (If you have changed the statedump-path replace the path in the above command) Regards, Karthik On Thu, Feb 6, 2020 at 5:06 PM Ulrich Pötter wrote: > Dear Gluster Users, > > we are running the following Gluster setup: > Replica 3 on 3 servers. Two are CentOs 7.6 with Gluster 6.5 and one was > upgraded to Centos 7.7 with Gluster 6.7. > > Since the upgrade to gluster 6.7 on one of the servers, we encountered > the following issue: > New healing entries appear and get healed, but soon afterwards new > healing entries appear. > The abovementioned problem started after we upgraded the server. > The healing issues do not only appear on the upgraded server, but on all > three. > > This does not seem to be a split brain issue as the output of the > command "gluster volume head info split-brain" is "number of > entries in split-brain: 0" > > Has anyone else observed such behavior with different Gluster versions > in one replica setup? > > We hesitate with updating the other nodes, as we do not know if this > standard Gluster behaviour or if there is more to this problem. > > Can you help us? > > Thanks in advance, > Ulrich > > > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/441850968 > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users > > Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Healing entries get healed but there are constantly new entries appearing
Dear Gluster Users, we are running the following Gluster setup: Replica 3 on 3 servers. Two are CentOs 7.6 with Gluster 6.5 and one was upgraded to Centos 7.7 with Gluster 6.7. Since the upgrade to gluster 6.7 on one of the servers, we encountered the following issue: New healing entries appear and get healed, but soon afterwards new healing entries appear. The abovementioned problem started after we upgraded the server. The healing issues do not only appear on the upgraded server, but on all three. This does not seem to be a split brain issue as the output of the command "gluster volume head info split-brain" is "number of entries in split-brain: 0" Has anyone else observed such behavior with different Gluster versions in one replica setup? We hesitate with updating the other nodes, as we do not know if this standard Gluster behaviour or if there is more to this problem. Can you help us? Thanks in advance, Ulrich Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Community Meeting: Make it more reachable
Hi, In response to the discussion that we had about the timings of the community meeting, I would like to propose that we can have it at 3PM/4PM IST on 11th February to accommodate EMEA/NA zone and if it suits all, we can fix the timing for next meetings as well. If anyone has any objections regarding this, it can be discussed in this thread so that we can come up with a fixed timing for the meeting. Regards, Yati On Thu, Jan 30, 2020 at 3:44 AM Sankarshan Mukhopadhyay < sankars...@kadalu.io> wrote: > > > On Wed, Jan 29, 2020, 17:14 Sunny Kumar wrote: > >> On Wed, Jan 29, 2020 at 9:50 AM Sankarshan Mukhopadhyay >> wrote: >> > >> > On Wed, 29 Jan 2020 at 15:03, Sunny Kumar wrote: >> > > >> > > Hello folks, >> > > >> > > I would like to propose moving community meeting to a time which is >> > > more suitable for EMEA/NA zone, that is merging both of the zone >> > > specific meetings into a single one. >> > > >> > >> > I am aware that there are 2 sets of meetings now - APAC and EMEA/NA. >> > This came about to ensure that users and community at these TZs have >> > the opportunity to participate in time slices that are more >> > comfortable. I have never managed to attend a NA/EMEA instance - is >> > that not seeing enough participation? There is only a very thin time >> >> I usually join but no one turns ups in meeting, I guess there is some >> sort of problem most likely no one is aware/hosting/communication gap. >> > > There certainly seems to be. Thanks for highlighting this situation. > > >> > slice that overlaps APAC, EMEA and NA. If we want to do this, we would >> > need to have a doodle/whenisgood set of options to see how this pans >> > out. >> >> Yes, we have to come up with a time which can cover most of TZs. >> > > Would be sending out a possible time slice set so that we can see how it > is accepted by those who are the regulars? > > In the meanwhile we can use the hackpad notes and the Slack channels to > ensure that the communication is improved. > ___ > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/441850968 > > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/441850968 > > Gluster-devel mailing list > gluster-de...@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel > > Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
