similar to: Announcing Glusterfs release 3.12.4 (Long Term Maintenance)

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

Any idea when these packages will be in the CentOS mirrors? there is no sign of them on download.gluster.org. On 13 October 2017 at 08:45, Jiffin Tony Thottan <jthottan at redhat.com> wrote: > The Gluster community is pleased to announce the release of Gluster 3.12.2 > (packages available at [1,2,3]). > > Release notes for the release can be found at [4]. > > We still

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 /export/birck1/test on each node. probes the two other systems from one node (a). abd created a replica 3

The Gluster community is pleased to announce the release of Gluster 3.12.2 (packages available at [1,2,3]). Release notes for the release can be found at [4]. We still carry following major issues 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

The Gluster community is pleased to announce the release of Gluster 3.12.6 (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, 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)

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

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, It's time to prepare the 3.12.8 release, which falls on the 10th of each month, and hence would be 12-04-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.7? 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)

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: >

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

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]

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, both Gluster servers were rebooted and now the unlink directory is clean. Best Regards Bernhard 2017-07-14 12:43 GMT+02:00 Bernhard D?bi <1linuxengineer at gmail.com>: > 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 * > >

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

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, 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)

On 14/07/17 13:06, Bernhard D?bi wrote: > Hello everybody, > > I'm in a similar situation as described in > https://bugzilla.redhat.com/show_bug.cgi?id=1374166 The issue got fixed by https://review.gluster.org/#/c/14820 and is already available in 3.8 branch > > I have a gluster volume exported through ganesha. we had some problems > on the gluster server and the NFS

Hello everybody, I'm in a similar situation as described in https://bugzilla.redhat.com/show_bug.cgi?id=1374166 I have a gluster volume exported through ganesha. we had some problems on the gluster server and the NFS mount on the client was hanging. I did a lazy umount of the NFS mount on the client, then went to the Gluster server, mounted the Gluster volume and deleted a bunch of files.