<p dir="ltr">No, it must be replicated or distributed-replicated for that.</p>
<p dir="ltr">On 7 May 2013 18:04, "Andrew Denton" <<a href="mailto:andrewd@sterling.net">andrewd@sterling.net</a>> wrote:<br>
><br>
> I'm testing out using gluster for storing backup images. I don't have<br>
> any data redundancy requirements beyond RAID, I just want the volume to<br>
> still be writable when one (or more?) nodes are down.<br>
><br>
> I tried it, but I'm getting a "transport endpoint is not connected"<br>
> error when I try to write to a volume where not all the servers are<br>
> reachable. Some writes fail, some writes succeed. I'm assuming this is<br>
> because the path hash points to the missing server. Is there some way to<br>
> get the client to try the write on another server? Currently I'm testing<br>
> 3.4.0-0.3.alpha3 on CentOS 6.4 (i686! my vintage test servers don't do<br>
> long mode unfortunately)<br>
><br>
> If I missed some documentation that talks about this, please point me to it!<br>
><br>
> Here are some specifics of what I tried:<br>
><br>
> [<a href="mailto:root@192.168.254.50">root@192.168.254.50</a> ~]# gluster volume info<br>
><br>
> Volume Name: testvol<br>
> Type: Distribute<br>
> Volume ID: 45db51e0-18ed-4180-882e-f208ffa01452<br>
> Status: Started<br>
> Number of Bricks: 4<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: 192.168.254.50:/mnt/brick1<br>
> Brick2: 192.168.254.51:/mnt/brick1<br>
> Brick3: 192.168.254.50:/mnt/brick2<br>
> Brick4: 192.168.254.51:/mnt/brick2<br>
><br>
> My client has testvol mounted:<br>
> 192.168.254.50:/testvol on /mnt/gluster-test type fuse.glusterfs<br>
> (rw,default_permissions,allow_other,max_read=131072)<br>
><br>
> I crudely killed all gluster services on 192.168.254.51 with "pkill<br>
> -KILL gluster".<br>
> From the other node,<br>
> [<a href="mailto:root@192.168.254.50">root@192.168.254.50</a> ~]# gluster peer status<br>
> Number of Peers: 1<br>
><br>
> Hostname: 192.168.254.51<br>
> Uuid: a9793617-3813-4721-a827-475790685f2c<br>
> State: Peer in Cluster (Disconnected)<br>
><br>
> Try to write to the volume from a client:<br>
><br>
> [root@client testvol]# dd if=/dev/zero of=foo bs=1M count=100<br>
> 100+0 records in<br>
> 100+0 records out<br>
> 104857600 bytes (105 MB) copied, 1.30653 s, 80.3 MB/s<br>
><br>
> [root@client testvol]# dd if=/dev/zero of=bar bs=1M count=100<br>
> dd: opening `bar': Transport endpoint is not connected<br>
><br>
> My client logs show entries like this:<br>
> [2013-05-07 16:47:14.776711] W [common-utils.c:2330:gf_ports_reserved]<br>
> 0-glusterfs-socket: is not a valid port identifier<br>
> [2013-05-07 16:47:14.776948] W [socket.c:514:__socket_rwv]<br>
> 0-testvol-client-1: readv failed (No data available)<br>
> [2013-05-07 16:47:14.779218] W [common-utils.c:2330:gf_ports_reserved]<br>
> 0-glusterfs-socket: is not a valid port identifier<br>
> [2013-05-07 16:47:14.779380] W [socket.c:514:__socket_rwv]<br>
> 0-testvol-client-3: readv failed (No data available)<br>
> [2013-05-07 16:47:16.732909] W<br>
> [client-rpc-fops.c:2624:client3_3_lookup_cbk] 0-testvol-client-1: remote<br>
> operation failed: Transport endpoint is not connected. Path: /<br>
> (00000000-0000-0000-0000-000000000001)<br>
><br>
><br>
><br>
> - Andrew<br>
><br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
</p>