Re: [Gluster-devel] reflink support for glusterfs and gluster-block using it for taking snapshots

On Tue, Nov 7, 2017 at 7:43 AM, Pranith Kumar Karampuri wrote: > hi, > I just created a github issue for reflink support(#349) in glusterfs. > We are intending to use this feature to do block snapshots in gluster-block. > > Please let us know your comments on the github

[Gluster-devel] reflink support for glusterfs and gluster-block using it for taking snapshots

hi, I just created a github issue for reflink support (#349) in glusterfs. We are intending to use this feature to do block snapshots in gluster-block. Please let us know your comments on the github issue. I have added the changes we may need

Re: [Gluster-devel] [Gluster-users] Request for Comments: Upgrades from 3.x to 4.0+

Ahh OK I see, thanks On 6 November 2017 at 00:54, Kaushal M wrote: > On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil > wrote: > > Just so I am clear the upgrade process will be as follows: > > > > upgrade all clients to 4.0 > > > > rolling upgrade all

Re: [Gluster-devel] Regression failure: ./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t

On Mon, 6 Nov 2017 at 18:26, Nithya Balachandran wrote: > On 6 November 2017 at 18:02, Atin Mukherjee wrote: > >> Snippet from where the test failed (the one which failed is marked in >> bold): >> >> # Start the >> volume >> TEST $CLI_1 volume start >>

Re: [Gluster-devel] Regression failure : /tests/basic/ec/ec-1468261.t

I don't think it is an issue with the test you mentioned. You may have to re-trigger the test. This is what I did for one of my patch. -- Ashish - Original Message - From: "Nithya Balachandran" To: "Gluster Devel" , "Xavi Hernandez"

[Gluster-devel] Coverity covscan for 2017-11-06-8aace739 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-11-06-8aace739 ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Regression failure: ./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t

On 6 November 2017 at 18:02, Atin Mukherjee wrote: > Snippet from where the test failed (the one which failed is marked in > bold): > > # Start the volume > > TEST $CLI_1 volume start $V0 > > > > EXPECT_WITHIN $PROCESS_UP_TIMEOUT "1" brick_up_status_1 $V0 $H1 > $B1/${V0}1 >

[Gluster-devel] Gluster Summit BOF - Rebalance

Hi, We had a BOF on Rebalance at the Gluster Summit to get feedback from Gluster users. - Performance has improved over the last few releases and it works well for large files. - However, it is still not fast enough on volumes which contain a lot of directories and small files. The bottleneck

[Gluster-devel] Regression failure : /tests/basic/ec/ec-1468261.t

Can someone take a look at this? The run was aborted ( https://build.gluster.org/job/centos6-regression/7232/console) Thanks, Nithya ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Regression failure: ./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t

Snippet from where the test failed (the one which failed is marked in bold): # Start the volume TEST $CLI_1 volume start $V0 EXPECT_WITHIN $PROCESS_UP_TIMEOUT "1" brick_up_status_1 $V0 $H1 $B1/${V0}1 EXPECT_WITHIN $PROCESS_UP_TIMEOUT "1" brick_up_status_1 $V0 $H2 $B2/${V0}2 EXPECT_WITHIN

Re: [Gluster-devel] Coverity fixes

One of the things I noticed is, if we make https://scan.coverity.com/projects/gluster-glusterfs as the source of truth for coverity issues, then the issue IDs will be constant. We can reference them. Also note that we should most probably focusing on 'High Impact' issues first for sure, than the

[Gluster-devel] Regression failure: ./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t

Hi, Can someone take a look at : https://build.gluster.org/job/centos6-regression/7231/ ? >From the logs: [2017-11-06 08:03:21.200177]:++ G_LOG:./tests/bugs/glusterd/bug-1345727-bricks-stop-on-no-quorum-validation.t: TEST: 26 1 brick_up_status_1 patchy 127.1.1.3 /d/backends/3/patchy3