Re: [Gluster-devel] Announcing Glusterfs release 3.12.2 (Long Term Maintenance)

Many thanks for testing, Alastair! The glusterfs-3.12.3-1 packages have now been marked for release into the normal gluster-3.12 repository of the CentOS Storage SIG. I expect that the packages will land on the mirrors during the day tomorrow. Niels On Mon, Dec 11, 2017 at 04:24:21PM -0500,

Re: [Gluster-devel] Snapshot aware Geo-replication

Can we re-visit this thread? Aravinda, Would be great to add it to github issues, so we can pursue this forward there. -Amar On Tue, Apr 5, 2016 at 2:48 PM, Aravinda wrote: > Hi, > > Gluster Snapshots and Geo-replication are not well integrated, lot of > steps to be

Re: [Gluster-devel] Announcing Glusterfs release 3.12.2 (Long Term Maintenance)

Neil I don;t know if this is adequate but I did run a simple smoke test today on the 3.12.3-1 bits. I installed the 3.12.3-1 but on 3 fresh install Centos 7 VMs created a 2G image files and wrote a xfs files system on them on each system mount each under /export/brick1, and created

Re: [Gluster-devel] [Gluster-users] How large the Arbiter node?

Hi, there is good suggestion here : http://docs.gluster.org/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/#arbiter-bricks-sizing Since the arbiter brick does not store file

[Gluster-devel] How large the Arbiter node?

Hi, I see gluster now recommends the use of an arbiter brick in "replica 2" situations. How large should this brick be? I understand only metadata is to be stored. Let's say total storage usage will be 5TB of mixed size files. How large should such a brick be? -- Sent from the Delta quadrant

[Gluster-devel] Coverity covscan for 2017-12-11-c7a3e0ba (master branch)

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

[Gluster-devel] Release 3.12.4 : Scheduled for the 12th of December

Hi, It's time to prepare the 3.12.4 release, which falls on the 10th of each month, and hence would be 12-12-2017 this time around. This mail is to call out the following, 1) Are there any pending *blocker* bugs that need to be tracked for 3.12.4? If so mark them against the provided tracker