[Gluster-users] Managing volumes is unreliable

Heggland, Christian Christian.Heggland at nov.com
Wed Oct 2 10:57:22 UTC 2013

Unsure if its recommended but you could try and do the following if the set command stops adding / removing settings:

1. Stop the volume
2. Edit the config file for that volume on each node ( /var/lib/glusterd/vols )
3. Start the volume again.

I've had to do this in order to update the access list since the set command stopped working.

Best Regards Christian

-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Maciej Galkiewicz
Sent: 2. oktober 2013 11:35
To: Gluster General Discussion List
Subject: [Gluster-users] Managing volumes is unreliable


I am using glusterfs with following scenario:
Multiple untrusted groups of clients (hosts) need access to shared storage. For each group a separate glusterfs volume is created with authentication based on IP addresses. Groups and clients are dynamically created/removed so there are a lot of operations on volumes like start, stop, info, set.

Unfortunately managing volumes with those command is quite unreliable.
I am affected by https://bugzilla.redhat.com/show_bug.cgi?id=1002422.

Is there any other suitable for my scenario way of using glusterfs which could reduce operations on volumes or somehow workaround this issue?

Maciej Gałkiewicz
Shelly Cloud Sp. z o. o., Sysadmin
http://shellycloud.com/, macias at shellycloud.com
KRS: 0000440358 REGON: 101504426
Gluster-users mailing list
Gluster-users at gluster.org

More information about the Gluster-users mailing list