[Gluster-users] Distributed-Replicated Volume working weird

Luciano Facchinelli facchinelli.luciano at gmail.com
Wed Apr 6 21:20:17 UTC 2016

Hi guys

I've a 4 nodes Distributed-Replicated volume (2x2) using GlusterFS 3.7.10
and it's working really weird.

Here is the info of the volume :

olume Name: testvol
Type: Distributed-Replicate
Volume ID: 160a47c4-df2a-4b2f-8e9b-2af8de1aa4b3
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Brick1: gluster1.test.com:/media/brick/brick_1
Brick2: gluster3.test.com:/media/brick/brick_3
Brick3: gluster2.test.com:/media/brick/brick_2
Brick4: gluster4.test.com:/media/brick/brick_4
Options Reconfigured:
performance.readdir-ahead: on
transport.address-family: inet

I mounted the volume and write 4 files in it. Those 4 files went to
gluster1 and gluster 3
And that happens whether its 1 file or 1000.

BUT if i copy a folder with files in it, that folder is created in
distributed and replicated correctly.

What could be wrong?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160406/1c92fb6e/attachment.html>

More information about the Gluster-users mailing list