Re: [Gluster-users] [Gluster-devel] Release 3.10.2: Scheduled for the 30th of April

Thanks Talur! Further, for 3.10.3 as well Talur will be leading the release management work and we intend to release it on time, this time :) Shyam On 05/14/2017 04:32 PM, Raghavendra Talur wrote: Glusterfs 3.10.2 has been tagged. Packages for the various distributions will be available in

Re: [Gluster-users] Release 3.11: RC0 has been tagged

Hi, Packages are available for testing from the following locations, 3.11.0rc0 packages are available in Fedora Rawhide (f27) Packages for fedora-26, fedora-25, epel-7, and epel-6 are available now from [5] Packages for Stretch/9 and Jessie are at [5] Reminder, 3.11.0rcX packages are

[Gluster-users] [Errno 5] Input/output error: '/abc/def/ghi.gz'

I am running: glusterfs 3.5.9 built on Mar 28 2016 07:10:17 Other volume info: Type: Distributed-Replicate Number of Bricks: 8 x 3 = 24 Transport-type: tcp Options Reconfigured: performance.cache-refresh-timeout: 30 performance.cache-size: 768MB cluster.quorum-type: auto

[Gluster-users] Order of Bricks

Hi, No one has any idea to reorder bricks to change the distribution of files in a replica 2 after adding a brick Mailed friday the problem Sent from MailDroid___ Gluster-users mailing list Gluster-users@gluster.org

[Gluster-users] Testing for gbench.

Hi all! A while back I created a benchmark kit for Gluster: https://github.com/gluster/gbench To run it just check the help file: [bturner@ben-laptop bt--0001]$ python GlusterBench.py -h Gluster Benchmark Kit Options: -h --help Print gbench options. -v

Re: [Gluster-users] Failure while upgrading gluster to 3.10.1

On Mon, 15 May 2017 at 11:58, Pawan Alwandi wrote: > Hi Atin, > > I see below error. Do I require gluster to be upgraded on all 3 hosts for > this to work? Right now I have host 1 running 3.10.1 and host 2 & 3 > running 3.6.2 > > # gluster v set all cluster.op-version 31001

[Gluster-users] Mounting GlusterFS volume in a client.

Hi List users I am trying to mount a GlusterFS server volume to a Gluster Client in /var directory. My intention is to connect a folder of webserver in Gluster client (/var/www/html/data) to the Gluster storage server. The size of remote Gluster storage

Re: [Gluster-users] Gluster and NFS-Ganesha - cluster is down after reboot

> On 15 May 2017, at 12:56 PM, Soumya Koduri wrote: > > > > On 05/12/2017 06:27 PM, Adam Ru wrote: >> Hi Soumya, >> >> Thank you very much for last response – very useful. >> >> I apologize for delay, I had to find time for another testing. >> >> I updated instructions

Re: [Gluster-users] Gluster arbiter with tier

On 05/15/2017 11:03 AM, Benjamin Kingston wrote: Are there any plans to enable tiering with arbiter enabled? There was a discussion on brick ordering in tiered volumes affecting arbiter brick placement [1] but nothing concrete turned out. I don't think this is being actively looked into at

Re: [Gluster-users] Reliability issues with Gluster 3.10 and shard

On 15 May 2017 at 11:01, Benjamin Kingston wrote: > I resolved this with the following settings, particularly disabling > features.ctr-enabled > That's odd. CTR should be enabled for tiered volumes. Was it enabled by default? > > olume Name: storage2 > Type:

Re: [Gluster-users] Reliability issues with Gluster 3.10 and shard

I resolved this with the following settings, particularly disabling features.ctr-enabled olume Name: storage2 Type: Distributed-Replicate Volume ID: adaabca5-25ed-4e7f-ae86-2f20fc0143a8 Status: Started Snapshot Count: 0 Number of Bricks: 3 x (2 + 1) = 9 Transport-type: tcp Bricks: Brick1:

Re: [Gluster-users] Reliability issues with Gluster 3.10 and shard

Shard translator is currently supported only for VM image store workload. -Krutika On Sun, May 14, 2017 at 12:50 AM, Benjamin Kingston wrote: > Hers's some log entries from nfs-ganesha gfapi > > [2017-05-13 19:02:54.105936] E [MSGID: 133010] >

Re: [Gluster-users] Failure while upgrading gluster to 3.10.1

Hi Atin, I see below error. Do I require gluster to be upgraded on all 3 hosts for this to work? Right now I have host 1 running 3.10.1 and host 2 & 3 running 3.6.2 # gluster v set all cluster.op-version 31001 volume set: failed: Required op_version (31001) is not supported On Mon, May 15,