Gluster users - Jul 2017 - Upgrading Gluster revision (3.8.12 to 3.8.13) caused underlying VM fs corruption

On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at gmail.com>
wrote:
> >
> > 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 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 give
log files may be?

> Diego
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>


-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170711/7dceb292/attachment.html>

Well it was probably caused by running replica 2 and doing online
upgrade. However I added brick, turned volume to replica 3 with
arbiter and got very strange issue I will mail to this list in a
moment...

Thanks.
-ps


On Tue, Jul 11, 2017 at 1:55 PM, Pranith Kumar Karampuri
<pkarampu at redhat.com> wrote:
>
>
> On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at
gmail.com> wrote:
>>
>> >
>> > 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 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 give
> log files may be?
>
>>
>> Diego
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
>
> --
> Pranith
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

Hi,


Doing online upgrade with replica 2 should be fine, i think there might be
something else causing the corruption.


--

Respectfully
Mahdi A. Mahdi

________________________________
From: gluster-users-bounces at gluster.org <gluster-users-bounces at
gluster.org> on behalf of Pavel Szalbot <pavel.szalbot at gmail.com>
Sent: Tuesday, July 11, 2017 3:29:48 PM
To: Pranith Kumar Karampuri
Cc: gluster-users
Subject: Re: [Gluster-users] Upgrading Gluster revision (3.8.12 to 3.8.13)
caused underlying VM fs corruption

Well it was probably caused by running replica 2 and doing online
upgrade. However I added brick, turned volume to replica 3 with
arbiter and got very strange issue I will mail to this list in a
moment...

Thanks.
-ps


On Tue, Jul 11, 2017 at 1:55 PM, Pranith Kumar Karampuri
<pkarampu at redhat.com> wrote:
>
>
> On Tue, Jul 11, 2017 at 5:12 PM, Diego Remolina <dijuremo at
gmail.com> wrote:
>>
>> >
>> > 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 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 give
> log files may be?
>
>>
>> Diego
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
>
> --
> Pranith
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170713/8e38c19f/attachment-0001.html>