Re: [Gluster-devel] [Gluster-users] Lot of EIO errors in disperse volume

Xavi, Thanks. Please let me know the functions that we need to track for any inconsistencies in the return codes from multiple bricks for issue 1. I will start doing that. 1. Why the write fails in first place Thanks and Regards, Ram -Original Message- From:

Re: [Gluster-devel] [Gluster-users] Lot of EIO errors in disperse volume

Hi Ram, On 20/01/17 08:02, Ankireddypalle Reddy wrote: Ashish, Thanks for looking in to the issue. In the given example the size/version matches for file on glusterfs4 and glusterfs5 nodes. The file is empty on glusterfs6. Now what happens if glusterfs5 goes down. Though the

[Gluster-devel] Ongoing network issues in the cage

Hello folks, The cage is seeing a network issue at the moment with packet loss for all servers hosted in there. We're likely to see a noticable problem with Gerrit and Jenkins today. Additionally, on Tuesday, 24th Jan at 24 Jan 2017 from 13:00 to 13:15 (UTC) there's a scheduled failover testing.

Re: [Gluster-devel] [Gluster-users] Lot of EIO errors in disperse volume

Xavi, Finally I am able to locate the files for which we are seeing the mismatch. [2017-01-19 21:20:10.002737] W [MSGID: 122056] [ec-combine.c:875:ec_combine_check] 0-glusterfsProd-disperse-0: Mismatching xdata in answers of 'LOOKUP' for f5e61224-17f6-4803-9f75-dd74cd79e248

[Gluster-devel] Regression failure: https://build.gluster.org/job/centos6-regression/2757/consoleFull

Hi, Can someone take a look at this? The test that failed is: tests/bugs/replicate/bug-1297695.t Thanks, Nithya ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Gerrit outage window on 21st Jan 2017

Quick reminder about this outage window. It's this weekend. On Mon, Jan 09, 2017 at 04:28:02PM +0530, Nigel Babu wrote: > Hello folks, > > We're announcing a downtime window for Gerrit (review.gluster.org) on Saturday > 21st Jan 2017 for 8 hours. This outage will be used to move Gerrit to CentOS

Re: [Gluster-devel] Priority based ping packet for 3.10

> The more relevant question would be with TCP_KEEPALIVE and TCP_USER_TIMEOUT > on sockets, do we really need ping-pong framework in Clients? We might need > that in transport/rdma setups, but my question is concentrating on > transport/rdma. In other words would like to hear why do we need

[Gluster-devel] Release 3.10: Branched!

Hi, Release 3.10 has been branched, the following commands give the required information about the branch and the tags. git branch -v --list release-3.10 git show v3.10.0alpha1 git show v3.11dev rfc.sh has been updated, see [1]. Onto next steps, 1) We (as in Kaleb and myself) have raised

Re: [Gluster-devel] Priority based ping packet for 3.10

On Thu, Jan 19, 2017 at 3:59 PM, Raghavendra G wrote: > The more relevant question would be with TCP_KEEPALIVE and > TCP_USER_TIMEOUT on sockets, do we really need ping-pong framework in > Clients? We might need that in transport/rdma setups, but my question is >

Re: [Gluster-devel] Priority based ping packet for 3.10

The more relevant question would be with TCP_KEEPALIVE and TCP_USER_TIMEOUT on sockets, do we really need ping-pong framework in Clients? We might need that in transport/rdma setups, but my question is concentrating on transport/rdma. In other words would like to hear why do we need heart-beat

Re: [Gluster-devel] FOP write success when volume of glusterfs is full with write-behind is on

On Fri, Jan 13, 2017 at 1:48 PM, Lian, George (Nokia - CN/Hangzhou) < george.l...@nokia.com> wrote: > Hi, > > I try write FOP test on case of volume of gusterfs is full, the detail > process and some investigation is as the below: > >

Re: [Gluster-devel] Priority based ping packet for 3.10

On Thu, Jan 19, 2017 at 1:50 PM, Mohammed Rafi K C wrote: > Hi, > > The patch for priority based ping packets [1] are ready to review. As > Shyam mentioned in the comment on patch set 12, it doesn't solve the > problem with network conjunction nor the disk latency. Also it