Hi Whit,
Thanks for your reply.
I do know that it's not the Gluster-standard thing to use a crossover
link.
(Seems to me it's the obvious best way to do it, but it's not a
configuration they're committed to.) It's possible that if you were
doing
your replication over the LAN rather than the
Daniel,
Can you confirm if you backend filesystem is proper? Can you delete the
file from the backend? Gluster does not return EROFS in any of the cases you
described. Also, try setting a lower ping-timeout and see if it helps in
case of crosscable failover test.
Avati
On Tue, Jun 14, 2011 at
Hi
Thanks for your reply.
Can you confirm if you backend filesystem is proper? Can you delete
the file from the backend?
I was able to delete files on the server.
Also, try setting a lower ping-timeout and see if
it helps in case of crosscable failover test.
I set it to 5 seconds, but
On Tue, Jun 14, 2011 at 2:51 AM, Daniel Manser dan...@clienta.ch wrote:
Hi
Thanks for your reply.
Can you confirm if you backend filesystem is proper? Can you delete
the file from the backend?
I was able to delete files on the server.
Also, try setting a lower ping-timeout and see if
I disconnected the crossover (replication) link again and it happened
again. When I re-connect it afterwards, it takes some seconds and
Gluster NFS works again. If this behavior is normal, then the
replication link becomes a single point of failure. Any suggestions?
On Mon, Jun 13, 2011 at 11:04:18AM +0100, Daniel Manser wrote:
I disconnected the crossover (replication) link again and it
happened again. When I re-connect it afterwards, it takes some
seconds and Gluster NFS works again. If this behavior is normal,
then the replication link becomes a single
Can you please share NFS and brick logs from the duration of the link going
down? Gluster should have worked in the situation you described.
Avati
On Fri, Jun 10, 2011 at 3:27 PM, Daniel Manser dan...@clienta.ch wrote:
Dear community,
I have a 2-node gluster cluster with one replicated
Can you please share NFS and brick logs from the duration of the link
going down? Gluster should have worked in the situation you
described.
Brick log on gluster1:
[2011-06-10 13:12:08.57634] W [socket.c:204:__socket_rwv]
0-tcp.vmware-server: readv failed (Connection timed out)
[2011-06-10
