Why this configuration does not work with GlusterFS 3.0?

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

 



Hi lesonus,

Please look for the logfiles, in the path suggested to your previous mail
and then send it to us.

regards,
On Sun, Jan 3, 2010 at 10:52 AM, lesonus <lesonus at gmail.com> wrote:

> I setup well glusterFS 3.0 in Centos 5.4 64 Bit
> But when I try old configuration of 2.06 version:
> *....
> volume unify
>  type cluster/unify
>  option scheduler rr # round robin
>  option namespace afr-ns
>  subvolumes afr1 afr2
> end-volume
> *
> Client not run, and I replaced  by this (  type cluster/unify ---->   type
> legacy/cluster/unify)
> *....
> volume unify
>  type *legacy/*cluster/unify
>  option scheduler rr # round robin
>  option namespace afr-ns
>  subvolumes afr1 afr2
> end-volume
> *
>
> But there other error, client can NOT connect to server, when I type
> command *df -H*:
> the result is:
> *df: `/mnt/glusterfs': Transport endpoint is not connected*
>
> How can I resolve this error!
>
> Thanks in advanced!
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>



-- 
Raghavendra G


[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