similar to: Release 3.12.8: Scheduled for the 12th of April

Dear Jiffin, Would it be possible to have the following backported to 3.12: https://bugzilla.redhat.com/show_bug.cgi?id=1482064 See my mail with subject "New 3.12.7 possible split-brain on replica 3" on the list earlier this week for more details. Thank you very much. Best regards, Mabi ??????? Original Message ??????? On April 11, 2018 5:16 AM, Jiffin Tony Thottan <jthottan at

Mabi, It looks like one of the patches is not a straight forward cherry-pick to the 3.12 branch. Even though the conflict might be easy to resolve, I don't think it is a good idea to hurry it for tomorrow. We will definitely have it ready by the next minor release (or if by chance the release is delayed and the back port is reviewed and merged before that). Hope that is acceptable.

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 to be tracked for 3.12.6? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2)

Hi, It's time to prepare the 3.12.5 release, which falls on the 10th of each month, and hence would be 12-01-2018 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.5? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2)

Hi, It's time to prepare the 3.12.2 release, which falls on the 10th of each month, and hence would be 10-10-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.2? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2)

Hi, I am planning to do 3.12.3 release today 10:00 pm IST (4:30 pm GMT). Following bugs is removed from tracker list Bug 1501235 - [SNAPSHOT] Unable to mount a snapshot on client -- based on discussion on gerrit, it can be target for 3.13 instead of the 3.12.x release Bug 1507006 - Read-only option is ignored and volume mounted in r/w mode -- assigned to none, no progress in master bug as

Hi, I wonder how this procedure works. I could add a bug that I think is a *blocker*, but there might not be consensus. Cheers, Hans Henrik On 11-01-2018 07:02, Jiffin Tony Thottan wrote: > Hi, > > It's time to prepare the 3.12.5 release, which falls on the 10th of > each month, and hence would be 12-01-2018 this time around. > > This mail is to call out the following,

On Thu, Oct 12, 2017 at 3:43 PM, Mohammed Rafi K C <rkavunga at redhat.com> wrote: > Hi Jiffin/Shyam, > > > Snapshot volume has been broken in 3.12 . We just got the bug, I have > send a patch [1] . Let me know your thought. > > > Similar with subdir mount's authentication. [2] [2] : https://review.gluster.org/#/c/18489/ > [1] :

Hi, I am planning to do 3.12.2 release today 11:00 pm IST (5:30 pm GMT). Following bugs is removed from tracker list Bug 1493422 - AFR : [RFE] Improvements needed in "gluster volume heal info" commands -- feature request will be target for 3.13 Bug 1497989 - Gluster 3.12.1 Packages require manual systemctl daemon reload after install -- "-1" from Kaleb, no progress from

Hi Jiffin/Shyam, Snapshot volume has been broken in 3.12 . We just got the bug, I have send a patch [1] . Let me know your thought. [1] : https://review.gluster.org/18506 On 10/12/2017 12:32 PM, Jiffin Tony Thottan wrote: > Hi, > > I am planning to do 3.12.2 release today 11:00 pm IST (5:30 pm GMT). > > Following bugs is removed from tracker list > > Bug 1493422 - AFR :

On Fri, Nov 10, 2017 at 11:23:51AM +0530, Jiffin Tony Thottan wrote: > Hi, > > I am planning to do 3.12.3 release today 10:00 pm IST (4:30 pm GMT). > > Following bugs is removed from tracker list > > Bug 1501235 - [SNAPSHOT] Unable to mount a snapshot on client -- based on > discussion on gerrit, it can be target for 3.13 > instead of the 3.12.x release > > Bug

The Gluster community is pleased to announce the release of Gluster 3.12.8 (packages available at [1,2,3]). Release notes for the release can be found at [4]. Thanks, Gluster community [1] https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.8/ [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 [3] https://build.opensuse.org/project/subprojects/home:glusterfs [4]

Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and

Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote: >

The Gluster community is pleased to announce the release of Gluster 3.12.4 (packages available at [1,2,3]). Release notes for the release can be found at [4]. We still carry following major issue that is reported in the release-notes as follows, 1.) - Expanding a gluster volume that is sharded may cause file corruption ??? Sharded volumes are typically used for VM images, if such volumes

Hi, On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: > Hi Jiffin, > > I looked at the document, and there are 2 things: > > 1. In Gluster 3.8 it seems you don't need to do that at all, it > creates this automatically, so why not in 3.10? Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 Regards, Jiffin [1]

Hey Niels, Installed 3.12.4 from centos-gluster312-test on my dev ovirt hyper converged cluster. Everything looks good and is working as expected for storage, migration, & healing. Need any specifics? -D > From: Jiffin Tony Thottan <jthottan at redhat.com> > Subject: [Gluster-users] Announcing Glusterfs release 3.12.4 (Long Term Maintenance) > Date: December 19, 2017 at

On 16/07/17 20:11, Bernhard D?bi wrote: > Hi, > > both Gluster servers were rebooted and now the unlink directory is clean. Following should have happened, If delete operation is performed gluster keeps file in .unlink directory if it has open fd. In this case since lazy umount is performed, ganesha server may still keep the fd's open by that client so gluster keeps the unlink

Hi, yes, I mounted the Gluster volume and deleted the files from the volume not the brick mount -t glusterfs hostname:volname /mnt cd /mnt/some/directory rm -rf * restart of nfs-ganesha is planned for tomorrow. I'll keep you posted BTW: nfs-ganesha is running on a separate server in standalone configuration Best Regards Bernhard 2017-07-14 10:43 GMT+02:00 Jiffin Tony Thottan <jthottan

On 12/10/17 16:05, Amar Tumballi wrote: > > > On Thu, Oct 12, 2017 at 3:43 PM, Mohammed Rafi K C > <rkavunga at redhat.com <mailto:rkavunga at redhat.com>> wrote: > > Hi Jiffin/Shyam, > > > Snapshot volume has been broken in 3.12 . We just got the bug, I have > send a patch [1] . Let me know your thought. > > > > Similar with