Crossover cable: single point of failure?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 14, 2011 at 2:51 AM, Daniel Manser <daniel at 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
>> it helps in case of crosscable failover test.
>
> I set it to 5 seconds, but the result is still the same.

It will be good to get to bottom of this. Do you see any errors in
server logs? Is it possible to do the same test with no vmware in
between, just using baremetals?

>
> ?Volume Name: vmware
> ?Type: Replicate
> ?Status: Started
> ?Number of Bricks: 2
> ?Transport-type: tcp
> ?Bricks:
> ?Brick1: gluster1:/mnt/gvolumes/vmware
> ?Brick2: gluster2:/mnt/gvolumes/vmware
> ?Options Reconfigured:
> ?network.ping-timeout: 5
>
> Daniel
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux