Re: [Gluster-users] [Gluster-devel] Release 3.12.6: Scheduled for the 12th of February

2018-02-02 Thread Nithya Balachandran
On 2 February 2018 at 11:16, Jiffin Tony Thottan wrote: > Hi, > > It's time to prepare the 3.12.6 release, which falls on the 10th of > each month, and hence would be 12-02-2018 this time around. > > This mail is to call out the following, > > 1) Are there any pending **blocker** bugs that need t

[Gluster-users] Announcing Gluster release 3.10.10 (Long Term Maintenance)

2018-02-02 Thread Shyam Ranganathan
The Gluster community is pleased to announce the release of Gluster 3.10.10 (packages available at [1]). Release notes for the release can be found at [2]. The corruption issue when sharded volumes are rebalanced, is fixed with this release. Thanks, Gluster community [1] Packages: https://downl

Re: [Gluster-users] How to trigger a resync of a newly replaced empty brick in replicate config ?

2018-02-02 Thread Serkan Çoban
If I were you I follow the following steps. Stop the rebalance and fix the cluster health first. Bring up the down server, replace server4:brick4 with a new disk, format and be sure it is started, then start a full heal. Without all bricks up full heal will not start. The you can continue with reba

Re: [Gluster-users] How to trigger a resync of a newly replaced empty brick in replicate config ?

2018-02-02 Thread Alessandro Ipe
Hi, I simplified the config in my first email, but I actually have 2x4 servers in replicate-distribute with each 4 bricks for 6 of them and 2 bricks for the remaining 2. Full healing will just take ages... for a just single brick to resync ! > gluster v status home volume status home Status