[Gluster-devel] [Fwd: [Gluster-infra] Regarding the recent arrival of emails on list]

(work better without a error in the address) -- Michael Scherer Sysadmin, Community Infrastructure --- Begin Message --- Hi, while working on https://bugzilla.redhat.com/show_bug.cgi?id=1730962, I did notice that no one was moderating the list since end of April, so I decided to clean the

Re: [Gluster-devel] Quick question about the latest glusterfs and client side selinux support

Thank you so much Jiffin for the quick response! -Janak From: Jiffin Thottan Sent: Thursday, June 20, 2019 11:58:52 PM To: Desai, Janak Cc: Gluster Devel; nfs-ganesha-devel Subject: Re: Quick question about the latest glusterfs and client side selinux support

Re: [Gluster-devel] [Gluster-users] No healing on peer disconnect - is it correct?

My VMs using Gluster as storage through libgfapi support in Qemu. But I dont see any healing of reconnected brick. Thanks Karthik / Ravishankar in advance! > On 10 Jun 2019, at 16:07, Hari Gowtham wrote: > > On Mon, Jun 10, 2019 at 7:21 PM snowmailer > wrote: >>

Re: [Gluster-devel] Failure during “git review –setup”

Never mind – It worked. The $USER when adding the remote gerrit should be my github user, documentation was not clear! From: Saleh, Amgad (Nokia - US/Naperville) Sent: Thursday, May 23, 2019 11:34 PM To: gluster-devel@gluster.org Subject: RE: Failure during “git review –setup” Importance: High

Re: [Gluster-devel] [Gluster-users] No healing on peer disconnect - is it correct?

Hi Martin, By default gluster will proactively start to heal every 10 min - so this is not OK. Usually, I do not wait for that to get triggered and i run gluster volume heal full (using replica 3 with sharding of 4 MB -> oVirt default). Best Regards, Strahil NikolovOn Jun 3, 2019 19:58,

Re: [Gluster-devel] No healing on peer disconnect - is it correct?

Can someone advice on this, please? BR! Dňa 3. 6. 2019 o 18:58 užívateľ Martin napísal: > Hi all, > > I need someone to explain if my gluster behaviour is correct. I am not sure > if my gluster works as it should. I have simple Replica 3 - Number of Bricks: > 1 x 3 = 3. > > When one of my

[Gluster-devel] No healing on peer disconnect - is it correct?

Hi all, I need someone to explain if my gluster behaviour is correct. I am not sure if my gluster works as it should. I have simple Replica 3 - Number of Bricks: 1 x 3 = 3. When one of my hypervisor is disconnected as peer, i.e. gluster process is down but bricks running, other two healthy

Re: [Gluster-devel] [Gluster-users] VMs blocked for more than 120 seconds

as per https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds. , the informational warning could be suppressed with : "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" Moreover, as per their website : "*This message is not an error*. It is an indication that a

Re: [Gluster-devel] [Gluster-users] VMs blocked for more than 120 seconds

Hi Krutika, > Also, gluster version please? I am running old 3.7.6. (Yes I know I should upgrade asap) I’ve applied firstly "network.remote-dio off", behaviour did not changed, VMs got stuck after some time again. Then I’ve set "performance.strict-o-direct on" and problem completly

Re: [Gluster-devel] [Gluster-users] Proposing to previous ganesha HA cluster solution back to gluster code as gluster-7 feature

IMO, you should keep storhaug and maintain it. At the beginning, we were with pacemaker and corosync. Then we move to storhaug with the upgrade to gluster 4.1.x. Now you are talking about going back like it was. Maybe it will be better with pacemake and corosync but the important is to have a

Re: [Gluster-devel] Improve stability between SMB/CTDB and Gluster (together with Samba Core Developer)

Hi Poornima, thats fine. I would suggest this dates and times: May 15th – 17th at 12:30, 13:30, 14:30 IST (9:00, 10:00, 11:00 CEST) May 20th – 24th at 12:30, 13:30, 14:30 IST (9:00, 10:00, 11:00 CEST) I add Volker Lendecke from Sernet to the mail. He is the Samba Expert. Can someone of you

Re: [Gluster-devel] [Gluster-users] VMs blocked for more than 120 seconds

Cache in qemu is none. That should be correct. This is full command : /usr/bin/qemu-system-x86_64 -name one-312 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e95a774e-a594-4e98-b141-9f30a3f848c1 -no-user-config -nodefaults

Re: [Gluster-devel] [Gluster-users] Proposing to previous ganesha HA clustersolution back to gluster code as gluster-7 feature

Hi, I'm posting this again as it got bounced. Keep in mind that corosync/pacemaker  is hard for proper setup by new admins/users. I'm still trying to remediate the effects of poor configuration at work. Also, storhaug is nice for hyperconverged setups where the host is not only hosting bricks,

Re: [Gluster-devel] [Gluster-users] Proposing to previous ganesha HA clustersolution back to gluster code as gluster-7 feature

Hi Jiffin, No vendor will support your corosync/pacemaker stack if you do not have proper fencing. As Gluster is already a cluster of its own, it makes sense to control everything from there. Best Regards, Strahil NikolovOn May 3, 2019 09:08, Jiffin Tony Thottan wrote: > > > On 30/04/19 6:59

Re: [Gluster-devel] Failure during “git review –setup”

Looking at the document https://gluster.readthedocs.io/en/latest/Developer-guide/Simplified-Development-Workflow/ I ran ./rfc.sh and got the following: [ahsaleh@null-d4bed9857109 glusterfs]$ ./rfc.sh % Total% Received % Xferd Average Speed TimeTime Time Current

[Gluster-devel] Invitation: End Date for Feature/Scope proposal for Release-7 @ Wed May 22, 2019 11am - 12pm (IST) (gluster-devel@gluster.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20190522T053000Z DTEND:20190522T063000Z DTSTAMP:20190515T065614Z ORGANIZER;CN=Gluster Rlease:mailto:redhat.com_r3hootcr6t1v4ag631ocgseshg@gr oup.calendar.google.com

[Gluster-devel] [Gluster-Maintainers] Release 7: Kick off!

It is time to start some activities for release-7. ## Scope It is time to collect and determine scope for the release, so as usual, please send in features/enhancements that you are working towards reaching maturity for this release to the devel list, and mark/open the github issue with the

[Gluster-devel] gluster-devel, rkoth...@redhat.com recommends that you use Google Calendar

I've been using Google Calendar to organize my calendar, find interesting events, and share my schedule with friends and family members. I thought you might like to use Google Calendar, too. rkoth...@redhat.com recommends that you use Google Calendar. To accept this invitation and register

Re: [Gluster-devel] [Gluster-users] Proposing to previous ganesha HA clustersolution back to gluster code as gluster-7 feature

Keep in mind that corosync/pacemaker is hard for proper setup by new admins/users. I'm still trying to remediate the effects of poor configuration at work. Also, storhaug is nice for hyperconverged setups where the host is not only hosting bricks, but other workloads. Corosync/pacemaker

Re: [Gluster-devel] [Gluster-users] Proposing to previous ganesha HA cluster solution back to gluster code as gluster-7 feature

+1! I'm using nfs-ganesha in my next upgrade so my client systems can use NFS instead of fuse mounts. Having an integrated, designed in process to coordinate multiple nodes into an HA cluster will very welcome. On April 30, 2019 3:20:11 AM EDT, Jiffin Tony Thottan wrote: >Hi all, > >Some of

Re: [Gluster-devel] [Gluster-users] gluster-block v0.4 is alive!

straight from ./autogen.sh && ./configure && make -j install CentOS Linux release 7.6.1810 (Core) May 17 19:13:18 vm2 gluster-blockd[24294]: Error opening log file: No such file or directory May 17 19:13:18 vm2 gluster-blockd[24294]: Logging to stderr. May 17 19:13:18 vm2

Re: [Gluster-devel] [Gluster-users] VMs blocked for more than 120 seconds

Hi, there is no healing operation, not peer disconnects, no readonly filesystem. Yes, storage is slow and unavailable for 120 seconds, but why, its SSD with 10G, performance is good. > you'd have it's log on qemu's standard output, If you mean /var/log/libvirt/qemu/vm.log there is nothing. I

Re: [Gluster-devel] [Gluster-users] VMs blocked for more than 120 seconds

what is the context from dmesg ? On Mon, May 13, 2019 at 7:33 AM Andrey Volodin wrote: > as per > https://helpful.knobs-dials.com/index.php/INFO:_task_blocked_for_more_than_120_seconds. > , > the informational warning could be suppressed with : > > "echo 0 >

Re: [Gluster-devel] [Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)

Amar, Thanks for the clarification. I'll go climb back into my cave. :) Harold On Fri, Apr 26, 2019 at 9:20 AM Amar Tumballi Suryanarayan < atumb...@redhat.com> wrote: > > > On Fri, Apr 26, 2019 at 6:27 PM Kaleb Keithley > wrote: > >> >> >> On Fri, Apr 26, 2019 at 8:21 AM Harold Miller

Re: [Gluster-devel] [Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)

Has Red Hat security cleared the Slack systems for confidential / customer information? If not, it will make it difficult for support to collect/answer questions. Harold Miller, Associate Manager, Red Hat, Enterprise Cloud Support Desk - US (650) 254-4346 On Fri, Apr 26, 2019 at 6:00 AM

Re: [Gluster-devel] [Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)

Hello, are you not _BOTH_ Red Hat FTEs or contractors? On Fri, Apr 26, 2019, 3:16 AM Michael Scherer wrote: > Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a > écrit : > > Hi All, > > > > We wanted to move to Slack from IRC for our official communication > > channel > >