Apologies in advance if this question is as basic as it feels. I'm trying
to understand options for expanding capacity on a volume of type
Replicate. I've been reading
http://www.gluster.org/community/documentation/index.php/Gluster_3.1:_Expanding_Volumes
and
Assuming you're saying you have a 2 brick replica 2 volume, adding two
more bricks will add distribution to your volume - making your volume a
distribute-replica volume, increasing your storage capacity.
On 07/22/2015 12:09 PM, Kevin Bridges wrote:
Apologies in advance if this question is as
perfect .. Thank you
On Wed, Jul 22, 2015 at 1:15 PM, Joe Julian j...@julianfamily.org wrote:
Assuming you're saying you have a 2 brick replica 2 volume, adding two
more bricks will add distribution to your volume - making your volume a
distribute-replica volume, increasing your storage
Hi Rafi,
It’s what I do. But I note particularly this kind of trouble when I mount my
volumes manually.
In addition, when I changed my transport-type from tcp or rdma to tcp,rdma, I
have had to restart my volume in order they can took effect.
I wonder if these trouble are not due to RDMA
… And, after a moment (a few minutes after having restarted my back-transfert
of around 40TB), my volume fall down (and all my rsync too):
[root@atlas ~]# df -h /mnt
df: « /mnt »: Noeud final de transport n'est pas connecté
df: aucun système de fichiers traité
aka transport endpoint is not
Oops, i forgot to add all people in CC.
Yes, i guessed.
With TCP protocol, all my volume seem OK and I dont note, for the moment, any
hang.
mount command:
- with RDMA: mount -t glusterfs -o
transport=rdma,direct-io-mode=disable,enable-ino32 ib-storage1:vol_home /mnt
- with
On 07/22/2015 12:55 PM, Geoffrey Letessier wrote:
Concerning the hang, I just saw this only once with TCP protocol but,
actually, RDMA seems to be in cause.
If you are mounting a tcp,rdma volume using tcp protocol, all the
communication will go through the tcp connection and rdma won't come
Minutes:
http://meetbot.fedoraproject.org/gluster-meeting/2015-07-22/gluster-meeting.2015-07-22-12.02.html
Minutes (text):
http://meetbot.fedoraproject.org/gluster-meeting/2015-07-22/gluster-meeting.2015-07-22-12.02.txt
Log:
I can confirm your words… Everything looks like OK with TCP proto and more-or-less unstable with RDMA one. But TCP is slower than RDMA protocol…In attachments you can find my volume mount log, all brick logs and several information concerning my vol_shared volume.Thanks in advance,GeoffreyPS:
Hi,
I have a wired situation. Is this as it should be? or what is going on
# gluster --version
glusterfs 3.6.2 built on Jan 22 2015 12:58:11
There are 8 files reported in split-brain (1024 times), but they seem to be
identical.
# gluster volume heal glu_rhevtst_dr2_data_01 info split-brain|
10 matches
Mail list logo
