Note sure who to notify.
ppa:gluster/glusterfs-3.10
glusterfs-server/xenial,now 3.10.5-ubuntu1~xenial1 amd64 [installed]
clustered file-system (server package)
I simply added the text file 'virt' with the settings from a RedHat7 install
performance.quick-read=off
performance.read-ahead=off
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-09-08-91cd0ed2
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Hey, so I ended up implementing this slightly differently.
Please take a look: https://review.gluster.org/#/c/18213/
On Tue, Jul 11, 2017 at 2:27 PM, Raghavendra Talur
wrote:
> On Tue, Jul 11, 2017 at 1:51 PM, Atin Mukherjee
> wrote:
> > If a patch is
On Fri, Sep 08, 2017 at 03:42:10PM +0530, Sachidananda URS wrote:
> On Fri, Sep 8, 2017 at 3:21 PM, Niels de Vos wrote:
>
> > Hi Sac,
> >
> > Could we setup a Jenkins job in the CentOS CI so that we can test
> > gdeploy automatically? Every time an update lands in the testing
On Fri, Sep 8, 2017 at 3:21 PM, Niels de Vos wrote:
> Hi Sac,
>
> Could we setup a Jenkins job in the CentOS CI so that we can test
> gdeploy automatically? Every time an update lands in the testing
> repositories, the job could run. The CentOS CI allows us to request a
> few
Hi Sac,
Could we setup a Jenkins job in the CentOS CI so that we can test
gdeploy automatically? Every time an update lands in the testing
repositories, the job could run. The CentOS CI allows us to request a
few machines at the same time, making it an ideal environment for
testing gdeploy.
If
I'm not sure if Gluster has any material impact. Would request the
Gluster project members who are also part of the CentOS Storage SIG to
confirm and/or respond to Karanbir.
-- Forwarded message --
From: Karanbir Singh
Date: Fri, Sep 8, 2017 at 4:08 AM
All I know is pump translator is written long back to support
'replace-brick' without data-loss in distributed setup too. But we figured
out pump is not maintainable along the way, and said you can't do a
replace-brick in distributed volume type.
It was used for testing pump xlator functionality. When replace-brick is
done on a distribute volume, it would lead to pump xlator migrating data to
the destination brick from source. I guess we can delete this test. I don't
think we support pump xlator anymore.
On Fri, Sep 8, 2017 at 10:02 AM,
Thanks all for the feedback!
On Sat, Sep 2, 2017 at 12:21 AM, John Strunk wrote:
>
>
> On Fri, Sep 1, 2017 at 1:27 AM, Amar Tumballi wrote:
>
>> Disclaimer: This email is long, and did take significant time to write.
>> Do take time and read, review and
10 matches
Mail list logo