Re: [Gluster-users] set: failed: Quorum not met. Volume operation not allowed.

[Karthik Subrahmanya]

Hi,

Since your two nodes are scrapped and there is no chance that they
will come back in later time, you can try reducing the replica count
to 1 by removing the down bricks from the volume and then mounting the
volume back to access the data which is available on the only up
brick.
The remove brick command looks like this:

gluster volume remove-brick VOLNAME replica 1
:/brick-path
:/brick-path force

Regards,
Karthik


On Thu, Aug 27, 2020 at 4:24 AM WK  wrote:
>
> So we migrated a number of VMs from a small Gluster 2+1A volume to a newer 
> cluster.
>
> Then a few days later the client said he wanted an old forgotten file that 
> had been left behind on the the deprecated system.
>
> However the arbiter and one of the brick nodes had been scraped, leaving only 
> a single gluster node.
>
> The volume I need uses shards so I am not excited about having to piece it 
> back together.
>
> I powered it up the single node and tried to mount the volume and of course 
> it refused to mount due to quorum and gluster volume status shows the volume 
> offline
>
> In the past I had worked around this issue by disabling quorum, but that was 
> years ago, so I googled it and found list messages suggesting the following:
>
>  gluster volume set VOL cluster.quorum-type none
>  gluster volume set VOL cluster.server-quorum-type none
>
> However, the gluster 6.9 system refuses to accept those set commands due to 
> the quorum and spits out the set failed error.
>
> So in modern Gluster, what is the preferred method for starting and mounting 
> a  single node/volume that was once part of a actual 3 node cluster?
>
> Thanks.
>
> -wk
>
>
> 
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users





Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Geo-replication force active server

[David Cunningham]

Hello,

We have geo-replication, and one of the nodes on the primary side (in
mirror replication with the other primary nodes), is acting a little badly.
These have been mentioned in other emails to the list about high CPU usage
and not closing log files.

At the moment it's hard to tell whether the problems are because this is
the active geo-replication push node, or if it's something else to do with
the server it's running on.

How can we force a particular node to be the active geo-replication push
node?

If we can make a different node the push and the problems move too, then we
know it's geo-replication and not the server that's the problem.

Thanks in advance,

-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] How safe are major version upgrades?

[Thomas Cameron]

On 8/26/2020 5:20 PM, David Cunningham wrote:

Thank you for that Hubert.

Does anyone know if an in-place upgrade between major versions is 
officially okay or not?


As a tangential question, what versions are safe to move from and to?

I've inherited an old CentOS 7 machine running an ancient version of 
Gluster (I want to say 3.x) from EPEL. Can I move from that to 7 
directly? Or do I need to go from 3 to 4 to 5 to 6 to 7?


Thomas




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] set: failed: Quorum not met. Volume operation not allowed.

[WK]

So we migrated a number of VMs from a small Gluster 2+1A volume to a 
newer cluster.


Then a few days later the client said he wanted an old forgotten file 
that had been left behind on the the deprecated system.


However the arbiter and one of the brick nodes had been scraped, leaving 
only a single gluster node.


The volume I need uses shards so I am not excited about having to piece 
it back together.


I powered it up the single node and tried to mount the volume and of 
course it refused to mount due to quorum and gluster volume status shows 
the volume offline


In the past I had worked around this issue by disabling quorum, but that 
was years ago, so I googled it and found list messages suggesting the 
following:


gluster volume set VOL cluster.quorum-type none
gluster volume set VOL cluster.server-quorum-type none

However, the gluster 6.9 system refuses to accept those set commands due 
to the quorum and spits out the set failed error.


So in modern Gluster, what is the preferred method for starting and 
mounting a  single node/volume that was once part of a actual 3 node 
cluster?


Thanks.

-wk






Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] How safe are major version upgrades?

[David Cunningham]

Thank you for that Hubert.

Does anyone know if an in-place upgrade between major versions is
officially okay or not?


On Thu, 27 Aug 2020 at 01:39, Hu Bert  wrote:

> Hi,
> we have 2 replicate-3 systems, and i upgraded both online from 5.12 to
> 6.8 and then to 7.6. No (big) problems here, upgrade took between 10
> to 20 minutes (wait until healing is done) - but no geo replication,
> so i can't say anything about that part.
>
> Best regards,
> Hubert
>
> Am Di., 25. Aug. 2020 um 05:47 Uhr schrieb David Cunningham
> :
> >
> > Hello,
> >
> > We have a production system with around 50GB of data running GlusterFS
> 5.13. It has 3 replicating/mirrored nodes, and also geo-replicates to
> another site.
> >
> > How safe would it be to upgrade to a more recent major version, eg 7.x?
> I'm not sure how recommended in-place upgrades are, or if a complete
> re-install is necessary for safety.
> >
> > We have a maximum window of around 4 hours for this upgrade and would
> not want any significant risk of an unsuccessful upgrade at the end of that
> time.
> >
> > Is version 8.0 considered stable?
> >
> > Thanks in advance,
> >
> > --
> > David Cunningham, Voisonics Limited
> > http://voisonics.com/
> > USA: +1 213 221 1092
> > New Zealand: +64 (0)28 2558 3782
> > 
> >
> >
> >
> > Community Meeting Calendar:
> >
> > Schedule -
> > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> > Bridge: https://bluejeans.com/441850968
> >
> > Gluster-users mailing list
> > Gluster-users@gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
>


-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] upgrade gluster from old version

[Hu Bert]

Hi,

i'd check the release logs of every x.0-version and the upgrade guide
if there are any params that are not supported anymore. If you have
one of these params set, you need to disable them, e.g.:

https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_6/


Best regards,
Hubert

Am Mi., 26. Aug. 2020 um 12:11 Uhr schrieb Sanju Rakonde :
>
> Hi,
>
> I believe you can do an offline upgrade (I have never tried upgrading from 
> 3.7 to 7.7, so there might be issues).
>
> If you want to do a fresh install, after installing the 7.7 packages, you can 
> use the same old bricks to create the volumes. but you need to add force at 
> the end of volume create command.
>
> On Wed, Aug 26, 2020 at 5:27 AM liu zhijing  wrote:
>>
>> hi everyone!
>> I found It is hard to upgrade  from a gluster version from 3.7.6 to 7.7,so I 
>> remove all the install package and delete all config file except the brick, 
>> and I resinstall the glusterfs 7.7, then reconfig the same volume name but 
>> use a temp brick.after everything is ok ,then i stop the volume and replace 
>> the old brick , change the brick volume id as the new volume id , at last  
>> start the volume successfully.
>> What I want to know is  if this is the right way to upgrade .
>>
>>
>> 
>>
>>
>>
>> Community Meeting Calendar:
>>
>> Schedule -
>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
>> Bridge: https://bluejeans.com/441850968
>>
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
> --
> Thanks,
> Sanju
> 
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] How safe are major version upgrades?

[Hu Bert]

Hi,
we have 2 replicate-3 systems, and i upgraded both online from 5.12 to
6.8 and then to 7.6. No (big) problems here, upgrade took between 10
to 20 minutes (wait until healing is done) - but no geo replication,
so i can't say anything about that part.

Best regards,
Hubert

Am Di., 25. Aug. 2020 um 05:47 Uhr schrieb David Cunningham
:
>
> Hello,
>
> We have a production system with around 50GB of data running GlusterFS 5.13. 
> It has 3 replicating/mirrored nodes, and also geo-replicates to another site.
>
> How safe would it be to upgrade to a more recent major version, eg 7.x? I'm 
> not sure how recommended in-place upgrades are, or if a complete re-install 
> is necessary for safety.
>
> We have a maximum window of around 4 hours for this upgrade and would not 
> want any significant risk of an unsuccessful upgrade at the end of that time.
>
> Is version 8.0 considered stable?
>
> Thanks in advance,
>
> --
> David Cunningham, Voisonics Limited
> http://voisonics.com/
> USA: +1 213 221 1092
> New Zealand: +64 (0)28 2558 3782
> 
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] upgrade gluster from old version

[Ramon Selga]

Tested several times recently: upgrade 3.12.15 to 7.7 without problems.

Upgrade servers and clients first to 3.12.15 ( old version, take a look to repo 
site).


If volumes are replicated you could do it on-line, one by one, looking carefully 
with self-heal process.


For disperse volumes you must stop them before upgrades.

Hope it helps!

Ramon


El 26/08/20 a les 12:04, Sanju Rakonde ha escrit:

Hi,

I believe you can do an offline upgrade (I have never tried upgrading from 3.7 
to 7.7, so there might be issues).


If you want to do a fresh install, after installing the 7.7 packages, you can 
use the same old bricks to create the volumes. but you need to add force at 
the end of volume create command.


On Wed, Aug 26, 2020 at 5:27 AM liu zhijing > wrote:


hi everyone!
I found It is hard to upgrade  from a gluster version from 3.7.6 to 7.7,so
I remove all the install package and delete all config file except the
brick, and I resinstall the glusterfs 7.7, then reconfig the same volume
name but use a temp brick.after everything is ok ,then i stop the volume
and replace the old brick , change the brick volume id as the new volume
id , at last  start the volume successfully.
What I want to know is  if this is the right way to upgrade .






Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org 
https://lists.gluster.org/mailman/listinfo/gluster-users



--
Thanks,
Sanju






Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users






Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] upgrade gluster from old version

[Sanju Rakonde]

Hi,

I believe you can do an offline upgrade (I have never tried upgrading from
3.7 to 7.7, so there might be issues).

If you want to do a fresh install, after installing the 7.7 packages, you
can use the same old bricks to create the volumes. but you need to add
force at the end of volume create command.

On Wed, Aug 26, 2020 at 5:27 AM liu zhijing  wrote:

> hi everyone!
> I found It is hard to upgrade  from a gluster version from 3.7.6 to 7.7,so
> I remove all the install package and delete all config file except the
> brick, and I resinstall the glusterfs 7.7, then reconfig the same volume
> name but use a temp brick.after everything is ok ,then i stop the volume
> and replace the old brick , change the brick volume id as the new volume id
> , at last  start the volume successfully.
> What I want to know is  if this is the right way to upgrade .
>
>
> 
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>


-- 
Thanks,
Sanju




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] How to fix I/O error ? (resend)

[Diego Zuccato]

Il 25/08/20 15:27, Amar Tumballi ha scritto:

> I am not aware of any data layout changes we did between current latest
> (7.7) and 3.8.8. But due to some issues, 'online' migration is not
> possible, even the clients needs to be updated, so you have to umount
> the volume once.
Tks for the info.
Actually the issue is less bad than I thought: I checked on a client
that (somehow) still used Debian oldstable. Current stable uses 5.5,
still old but not prehistoric :)

Too bad the original issue still persists, even after removing the file
and its hardlink from .gluster dir :(
Maybe the upgrade can fix it? Or I risk breaking it even more?

-- 
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786




Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users