search for: nixpan

...rent > op-version? > > He is not changing mayor versions, just a small step from 3.8.12 to > 3.8.13. Corruption should not be happening. > For some reason 3.8 upgrade guide is not where it is supposed to be. We highly recommend upgrading servers ahead of clients. https://github.com/nixpanic/glusterdocs/commit/f6d48dc17f2cb6ee4680e372520ec3358641b2bc I think at some point it is better to make this mandatory. Without a predefined way of upgrading, it is very difficult to fix bugs in backward compatible manner. I am not sure why the corruption happened either :-(. Pavel, could you gi...

On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara <paolo.margara at polito.it> wrote: > Hi Pranith, > > I'm using this guide https://github.com/nixpanic/glusterdocs/blob/ > f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md > > Definitely my fault, but I think that is better to specify somewhere that > restarting the service is not enough simply because in many other case, > with other services, is sufficient....

...29/06/2017 16:27, Pranith Kumar Karampuri ha scritto: > > > On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara > <paolo.margara at polito.it <mailto:paolo.margara at polito.it>> wrote: > > Hi Pranith, > > I'm using this guide > https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md > <https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md> > > Definitely my fault, but I think that is better to specify...

Hi Pranith, I'm using this guide https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md Definitely my fault, but I think that is better to specify somewhere that restarting the service is not enough simply because in many other case, with other services, is sufficient. Now I'm restarting...

...>> He is not changing mayor versions, just a small step from 3.8.12 to >> 3.8.13. Corruption should not be happening. > > > For some reason 3.8 upgrade guide is not where it is supposed to be. > We highly recommend upgrading servers ahead of clients. > https://github.com/nixpanic/glusterdocs/commit/f6d48dc17f2cb6ee4680e372520ec3358641b2bc > > I think at some point it is better to make this mandatory. Without a > predefined way of upgrading, it is very difficult to fix bugs in backward > compatible manner. > > I am not sure why the corruption happened eit...

...------------------- Message: 1 Date: Wed, 8 Mar 2017 22:44:15 +0100 From: Niels de Vos <ndevos at redhat.com> To: centos-announce at centos.org Subject: [CentOS-announce] Announcing the release for Gluster 3.10 on CentOS Linux 6 x86_64 Message-ID: <20170308214415.GA1546 at chromebook.lan.nixpanic.net> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 3.10 for CentOS 6 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 3.10 is a Long-Term-Maint...

[from http://blog.nixpanic.net/2017/08/last-update-for-gluster-38.html and also available on https://planet.gluster.org/ ] GlusterFS 3.8.15 is available, likely the last 3.8 update The next Long-Term-Maintenance release for Gluster is around the corner. Once GlusterFS-3.12 is available, the oldest maintained version...

> > You should first upgrade servers and then clients. New servers can > understand old clients, but it is not easy for old servers to understand new > clients in case it started doing something new. But isn't that the reason op-version exists? So that regardless of client/server mix, nobody tries to do "new" things above the current op-version? He is not changing mayor

[Repost of a clickable blog to make it easier to read over email http://blog.nixpanic.net/2017/06/glusterfs-3813-update-available.html and also expected to arrive on https://planet.gluster.org/ soon. The release notes can also be found in the release-3.8 branch on GitHub https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8.13.md] The Gluster releases...

...use-client. Untested patches for that are in the work-in-progress repository on the forge. Anyone who feels like testing and/or helping out is more than welcome. Thanks, Niels [ndevos on #gluster and #gluster-dev on IRC/Freenode] [0] https://forge.gluster.org/cloudstack-gluster [1] http://blog.nixpanic.net/2013/12/using-gluster-as-primary-storage-in.html [2] http://thread.gmane.org/gmane.comp.apache.cloudstack.devel/33878

[From http://blog.nixpanic.net/2017/07/glusterfs-3814-is-here.html and also on https://planet.gluster.org/] GlusterFS 3.8.14 is here, 3.8 even closer to End-Of-Life The 10th of the month has passed again, that means a 3.8.x update can't be far out. So, here it is, we're announcing the [9]availability of...

...--------------------- Message: 1 Date: Thu, 28 Mar 2019 15:48:42 +0100 From: Niels de Vos <ndevos at redhat.com> To: centos-announce at centos.org Subject: [CentOS-announce] Announcing the release of Gluster 6 on CentOS Linux 7 x86_64 Message-ID: <20190328144842.GD2572 at ndevos-x270.lan.nixpanic.net> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 6 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 6 is expected to receive upd...

On Mon, Jul 10, 2017 at 10:33 PM, Mahdi Adnan <mahdi.adnan at outlook.com> wrote: > I upgraded from 3.8.12 to 3.8.13 without issues. > > Two replicated volumes with online update, upgraded clients first and > followed by servers upgrade, "stop glusterd, pkill gluster*, update > gluster*, start glusterd, monitor healing process and logs, after > completion proceed to

...------------------ Message: 1 Date: Mon, 19 Mar 2018 20:16:50 +0100 From: Niels de Vos <ndevos at redhat.com> To: centos-announce at centos.org Subject: [CentOS-announce] Announcing the release for Gluster 4.0 on CentOS Linux 7 x86_64 Message-ID: <20180319191650.GJ2528 at ndevos-x270.lan.nixpanic.net> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 4.0 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 4.0 is a Short-Term-Mainte...

Paolo, Which document did you follow for the upgrade? We can fix the documentation if there are any issues. On Thu, Jun 29, 2017 at 2:07 PM, Ravishankar N <ravishankar at redhat.com> wrote: > On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > - put node in maintenance mode (ensure no client are active)

On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > * put node in maintenance mode (ensure no client are active) > * yum versionlock delete glusterfs* > * service glusterd stop > * yum update > * systemctl daemon-reload > * service glusterd start > * yum versionlock add glusterfs* > *