The volume stop, in brick-mux mode reveals a race with my patch [1]
Although this behavior is 100% reproducible with my patch, this, by no
means, implies that my patch is buggy.
In brick-mux mode, during volume stop, when glusterd sends a brick-detach
message to the brick process for the last bric
Hello,
Centos CI has a run-tests-in-vagrant job. Do we continue to need this
anymore? It still runs master and 3.8. I don't see this job adding much
value at this point given we only look at results that are on
build.gluster.org. I'd like to use the extra capacity for other tests that
will run on
I've started marking "whiteboard" of bugs in this class with tag
"GLUSTERFS_METADATA_INCONSISTENCY". Please add the tag to any bugs which
you deem to fit in.
On Fri, Feb 9, 2018 at 4:30 PM, Raghavendra Gowdappa
wrote:
>
>
> - Original Message -
> > From: "Pranith Kumar Karampuri"
> > To
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-02-13-e67cd078
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
