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

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)

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.

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

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

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

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

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

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

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

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

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

On Thu, Oct 26, 2017 at 2:24 AM, Marcin Dulak <marcin.dulak at gmail.com> wrote: > Hi, > > since people are suggesting nagios then I can't resist suggesting exporting > the metrics in the prometheus format, > or at least making the project into a library so > https://github.com/prometheus/client_python could be used to export the > prometheus metrics. > There has

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]

On Fri, Jun 5, 2015 at 1:33 PM, kunaal jain <kunaalus at gmail.com> wrote: > Can you tell us about Fedora Docs toolchain? We can surely help each other > if our interests align. > <https://fedorahosted.org/documentation-guide/> -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay>

Hello! I am attempting to setup a Gluster install using Ganesha for NFS using the guide found here http://blog.gluster.org/2015/10/linux-scale-out-nfsv4-using-nfs-ganesha-and-glusterfs-one-step-at-a-time/ The Gluster portion is working fine, however when I try to setup Ganesha I have a problem. The guide says to run 'gluster nfs-ganesha enable' however when I do, I get the following

Hi, Lei and I have been working on the project, based on community input. We have implemented two way sync between github and pagure as suggest by many. Now we want build the site and display it to user. There are number of options mkdocs, hugo(docker uses it now) etc. There are pros and cons to each site generator. To use hugo, we need the user to have hugo installed too, and than he needs to

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

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