similar to: pcs resources

Hi, I'm setting up gluster on a 2 node system. The setup is working, I configured pcsd and it's working, and I added the virtual_IP resource. However, on many examples on the net (for example: the output in this thread: https://www.centos.org/forums/viewtopic.php?t=60001 ) I see few resources in the pcs. Is this something which is being created automatically? or is it something that I

Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote: >

Hi, On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: > Hi Jiffin, > > I looked at the document, and there are 2 things: > > 1. In Gluster 3.8 it seems you don't need to do that at all, it > creates this automatically, so why not in 3.10? Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 Regards, Jiffin [1]

Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and

I checked, and I have it like this: # Name of the HA cluster created. # must be unique within the subnet HA_NAME="ganesha-nfs" # # The gluster server from which to mount the shared data volume. HA_VOL_SERVER="tlxdmz-nfs1" # # N.B. you may use short names or long names; you may not use IP addrs. # Once you select one, stay with it as it will be mildly unpleasant to # clean up

Hi, In your ganesha-ha.conf do you have your virtual ip adresses set something like this?: VIP_tlxdmz-nfs1="192.168.22.33" VIP_tlxdmz-nfs2="192.168.22.34" Renaud De?: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] De la part de Hetz Ben Hamo Envoy??: 20 d?cembre 2017 04:35 ??: gluster-users at gluster.org Objet?: [Gluster-users]

On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: > HI, > > I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. > > I'm trying to create a very simple 2 nodes cluster to be used with > NFS-ganesha. I've created the bricks and the volume. Here's the output: > > # gluster volume info > > Volume Name: cluster-demo > Type:

On 16/07/17 20:11, Bernhard D?bi wrote: > Hi, > > both Gluster servers were rebooted and now the unlink directory is clean. Following should have happened, If delete operation is performed gluster keeps file in .unlink directory if it has open fd. In this case since lazy umount is performed, ganesha server may still keep the fd's open by that client so gluster keeps the unlink

Dear Jiffin, Would it be possible to have the following backported to 3.12: https://bugzilla.redhat.com/show_bug.cgi?id=1482064 See my mail with subject "New 3.12.7 possible split-brain on replica 3" on the list earlier this week for more details. Thank you very much. Best regards, Mabi ??????? Original Message ??????? On April 11, 2018 5:16 AM, Jiffin Tony Thottan <jthottan at

Mabi, It looks like one of the patches is not a straight forward cherry-pick to the 3.12 branch. Even though the conflict might be easy to resolve, I don't think it is a good idea to hurry it for tomorrow. We will definitely have it ready by the next minor release (or if by chance the release is delayed and the back port is reviewed and merged before that). Hope that is acceptable.

Hi, both Gluster servers were rebooted and now the unlink directory is clean. Best Regards Bernhard 2017-07-14 12:43 GMT+02:00 Bernhard D?bi <1linuxengineer at gmail.com>: > Hi, > > yes, I mounted the Gluster volume and deleted the files from the > volume not the brick > > mount -t glusterfs hostname:volname /mnt > cd /mnt/some/directory > rm -rf * > >

Hi, yes, I mounted the Gluster volume and deleted the files from the volume not the brick mount -t glusterfs hostname:volname /mnt cd /mnt/some/directory rm -rf * restart of nfs-ganesha is planned for tomorrow. I'll keep you posted BTW: nfs-ganesha is running on a separate server in standalone configuration Best Regards Bernhard 2017-07-14 10:43 GMT+02:00 Jiffin Tony Thottan <jthottan

Hi, I've just created again the gluster with NFS ganesha. Glusterfs version 3.8 When I run the command gluster nfs-ganesha enable - it returns a success. However, looking at the pcs status, I see this: [root at tlxdmz-nfs1 ~]# pcs status Cluster name: ganesha-nfs Stack: corosync Current DC: tlxdmz-nfs2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum Last updated: Wed Dec 20

> > > On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz > <mailto:hetz at hetz.biz>> wrote: > > Hi Amar, > > If can say something about the development of GlusterFS - is that > there are 2 missing things: > > 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 > because someone [removed]

Hey Niels, Installed 3.12.4 from centos-gluster312-test on my dev ovirt hyper converged cluster. Everything looks good and is working as expected for storage, migration, & healing. Need any specifics? -D > From: Jiffin Tony Thottan <jthottan at redhat.com> > Subject: [Gluster-users] Announcing Glusterfs release 3.12.4 (Long Term Maintenance) > Date: December 19, 2017 at

On Tue, Jan 2, 2018 at 4:09 AM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > >> >> On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz <mailto: >> hetz at hetz.biz>> wrote: >> >> Hi Amar, >> >> If can say something about the development of GlusterFS - is that >> there are 2 missing things:

On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz> wrote: > Hi Amar, > > If can say something about the development of GlusterFS - is that there > are 2 missing things: > > 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because > someone support to enable NFS-Ganesha. from the gluster command has been > vanished without

Any idea when these packages will be in the CentOS mirrors? there is no sign of them on download.gluster.org. On 13 October 2017 at 08:45, Jiffin Tony Thottan <jthottan at redhat.com> wrote: > The Gluster community is pleased to announce the release of Gluster 3.12.2 > (packages available at [1,2,3]). > > Release notes for the release can be found at [4]. > > We still

Hi, Can u please explain for what purpose pacemaker cluster used here? Regards, Jiffin On Thursday 07 December 2017 06:59 PM, Tomalak Geret'kal wrote: > > Hi guys > > I'm wondering if anyone here is using the GlusterFS OCF resource > agents with Pacemaker on CentOS 7? > > yum install centos-release-gluster > yum install glusterfs-server

On 07/12/2017 13:47, Hetz Ben Hamo wrote: > Out of curiosity,? did you write it or you found those > commands somewhere else? I wrote it, using what little experience of pcs I have so far - haven't actually been able to find any documented steps/instructions. :( Although this blog - http://www.tomvernon.co.uk/blog/2015/01/gluster-activepassive-cluster/ - suggested I was on the right