similar to: Glusterfs 3.10.3 has been tagged

Apologies for delay in sending mail about builds. We have packages ready for all distributions, thanks to Kaleb and Niels. As per [1] (mostly[2]): * Packages for Fedora 24 and Fedora 27 are available at [3]. * Packages for Fedora 25 and Fedora 26 are built and queued in Fedora bodhi for testing. Once pushed to testing they will be available in the Updates-Testing repo. After a nominal testing

On Fri, 18 Aug 2017 at 13:45, Raghavendra Talur <rtalur at redhat.com> wrote: > On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: > > > > > > On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> > > wrote: > >> > >> You're hitting a race here. By the time glusterd tries to

Did the logs provide any hints as to what the issue may be? Diego On Sat, Jun 3, 2017 at 12:16 PM, Diego Remolina <dijuremo at gmail.com> wrote: > Thanks for taking the time to look into this. Since we needed downtime > due to the gluster update, we also updated the OS, including samba. We > went from 4.2.x to 4.4.4 and many other packages for CentOS were > updated as well. OS

Hi All, Kubernetes and Openshift have amazing projects called minikube and minishift which make it very easy to setup those distributed systems for easy development. As the Gluster ecosystem grows, we have more external projects which require easy setup of multi node Gluster cluster. Hence, along those lines, I introduce to you...minister (mini + Glu"ster"). Please do check out the

Awesome! You're on the list. Anyone else want to present? - amye On Fri, Nov 3, 2017 at 3:01 AM, Raghavendra Talur <rtalur at redhat.com> wrote: > I propose a talk > > "Life of a gluster client process" > > We will have a look at one complete life cycle of a client process > which includes: > * mount script and parsing of args > * contacting glusterd

Hi all! Based on the popularity of wanting more lightning talks at Gluster Summit, we'll be trying something new: Gluster Developer Conversations. This will be a one hour meeting on November 28th at UTC 15:00, with five 5 minute lightning talks and time for discussion in between. The meeting will be recorded, and I'll be posting the individual talks separately in our community channels.

Thanks for taking the time to look into this. Since we needed downtime due to the gluster update, we also updated the OS, including samba. We went from 4.2.x to 4.4.4 and many other packages for CentOS were updated as well. OS and samba updates were installed, then server rebooted, then gluster was updated. Created a new test samba share to minimize logs, etc: [VfsGluster] path = /vfsgluster

Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I went ahead and created a new share in the samba server which is on a local filesystem where the OS is installed, not part of gluster: # mount | grep home ]# ls -ld /home

I propose a talk "Life of a gluster client process" We will have a look at one complete life cycle of a client process which includes: * mount script and parsing of args * contacting glusterd and fetching volfile * loading and initializing the xlators * how glusterd sends updates of volume options * brick disconnection/reconnection * glusterd disconnection/reconnection * termination of

On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I don't think it is vfs plugin because you haven't updated samba packages

On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > > > On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: >> >> You're hitting a race here. By the time glusterd tries to resolve the >> address of one of the remote bricks of a particular volume, the n/w >> interface is not up by that

18.08.2017 12:21, Atin Mukherjee ?????: > > On Fri, 18 Aug 2017 at 13:45, Raghavendra Talur <rtalur at redhat.com > <mailto:rtalur at redhat.com>> wrote: > > On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee > <amukherj at redhat.com <mailto:amukherj at redhat.com>> wrote: > > > > > > On Fri, Aug 18, 2017 at 12:22 PM,

On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > You're hitting a race here. By the time glusterd tries to resolve the > address of one of the remote bricks of a particular volume, the n/w > interface is not up by that time. We have fixed this issue in mainline and > 3.12 branch through the following commit: > Correction. This patch is

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I

Hi Talur, I've successfully got Gluster deployed as a DaemonSet using k8s spec file glusterfs-daemonset.json from https://github.com/heketi/heketi/tree/master/extras/kubernetes but then when I try deploying heketi using heketi-deployment.json spec file, I end up with a CrashLoopBackOff pod. # kubectl get pods NAME READY STATUS RESTARTS AGE

Hello? We have used glusterfs3.4 with the lasted samba-glusterfs-vfs lib to test samba performance in windows client. two glusterfs server nodes export share with name of "gvol": hardwares: brick use a raid 5 logic disk with 8 * 2T SATA HDDs 10G network connection one linux client mount the "gvol" with cmd: [root at localhost current]# mount.cifs //192.168.100.133/gvol

On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch> wrote: Anyone? -------- Original Message -------- Subject: Persistent storage for docker containers from a Gluster volume Local Time: June 25, 2017 6:38 PM UTC Time: June 25, 2017 4:38 PM From: mabi at protonmail.ch To: Gluster Users <gluster-users at gluster.org> Hello, I have a two node replica 3.8 GlusterFS

Hi, glusterFS is working fine for large files (in most of the cases it's used for VM image store), with docker you'll generate bunch of small size files and if you want to have a good performance may be look in [1] and [2]. Also two node replica is a bit dangerous in case of high load with small files there is a good risk of split brain situation, therefore think about arbiter

----- Original Message ----- > From: "Zhang Huan" <zhanghuan at open-fs.com> > To: "Raghavendra G" <raghavendra at gluster.com> > Cc: "GlusterFS Maintainers" <maintainers at gluster.org>, "Gluster Devel" <gluster-devel at gluster.org>, "Kaushal Madappa" > <kmadappa at redhat.com> > Sent: Tuesday, May 30,

Heketi v5.0.1 is now available. This release[1] fixes a flaw that was found in heketi API that permits issuing of OS commands through specially crafted requests, possibly leading to escalation of privileges. More details can be obtained at CVE-2017-15103. [2] If authentication is turned "on" in heketi configuration, the flaw can be exploited only by those who possess authentication