*I use this configuration of client, it run well on Gluster 2.06. but not well with Gluster 3.0:* #--------------------------------------------------------------------------- ### Add client feature and attach to remote subvolume of server1 volume brick1 type protocol/client option transport-type tcp/client option remote-host 11.0.0.19 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server2 volume brick2 type protocol/client option transport-type tcp/client option remote-host 11.0.0.20 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server3 volume brick3 type protocol/client option transport-type tcp/client option remote-host 11.0.0.21 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server4 volume brick4 type protocol/client option transport-type tcp/client option remote-host 11.0.0.22 # IP address of the remote brick option remote-subvolume brick # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server1 volume brick1-ns type protocol/client option transport-type tcp/client option remote-host 11.0.0.19 # IP address of the remote brick option remote-subvolume brick-ns # name of the remote volume end-volume ### Add client feature and attach to remote subvolume of server2 volume brick2-ns type protocol/client option transport-type tcp/client option remote-host 11.0.0.20 # IP address of the remote brick option remote-subvolume brick-ns # name of the remote volume end-volume volume afr1 type cluster/afr subvolumes brick1 brick4 end-volume volume afr2 type cluster/afr subvolumes brick2 brick3 end-volume volume afr-ns type cluster/afr subvolumes brick1-ns brick2-ns end-volume volume unify type cluster/unify option scheduler rr # round robin option namespace afr-ns subvolumes afr1 afr2 end-volume #--------------------------------------------------------------------------- I also replace *"type cluster/unify" *by *"type legacy/cluster/unify"*, but error still, and error log like that: .................... 63: 64: volume unify 65: type legacy/cluster/unify 66: option scheduler rr # round robin 67: option namespace afr-ns 68: subvolumes afr1 afr2 69: end-volume +------------------------------------------------------------------------------+ [2010-01-04 00:02:19] C [unify.c:4361:init] unify: Namespace node should not be a child of any other node. Exiting [2010-01-04 00:02:19] E [xlator.c:838:xlator_init_rec] unify: Initialization of volume 'unify' failed, review your volfile again [2010-01-04 00:02:19] E [unify.c:4467:init] unify: initializing namespace node failed, Exiting [2010-01-04 00:02:19] E [xlator.c:838:xlator_init_rec] unify: Initialization of volume 'unify' failed, review your volfile again [2010-01-04 00:02:19] E [glusterfsd.c:583:_xlator_graph_init] glusterfs: initializing translator failed [2010-01-04 00:02:19] E [glusterfsd.c:1347:main] glusterfs: translator initialization failed. exiting * Please help me Fix this problem! Thanks in advanced!*
