[Gluster-users] questions about volfile (dangling volume warning)

Krishna Srinivas krishna at zresearch.com
Wed Dec 17 18:09:15 UTC 2008


Brian,

Ignore that warning. It is a false alarm, we will fix it.

Krishna

On Tue, Dec 16, 2008 at 10:27 PM, Brian Hirt <bhirt at mobygames.com> wrote:
> Hello,
>
> The setup is as follows.  4 machines are participating as both clients
> and servers uning AFR and unify.   Two replicated volumes
> (brick1,brick3) and (brick2,brick4) are unified into a single volume.
> I'm testing with 1.4RC3.
>
> When I mount the unified filesystem, I get this warning on the
> namespace volume:
>        2008-12-16 10:38:53 W [afr.c:1862:init] afr-ns: dangling volume.
> check volfile
>
> Does anyone have advice on what is set up incorrectly?
>
> ****Server****
>
> volume brick-store
>  type storage/posix
>  option directory /moby/gluster/
> end-volume
>
> volume brick
>   type features/locks
>   subvolumes brick-store
> end-volume
>
> volume brick-store-ns
>  type storage/posix
>  option directory /moby/gluster-ns/
> end-volume
>
> volume brick-ns
>  type features/locks
>  subvolumes brick-store-ns
> end-volume
>
> volume server
>  type protocol/server
>  option transport-type tcp/server
>  subvolumes brick brick-ns
>  option auth.addr.brick.allow x.x.x.* # Allow access to "brick" volume
>  option auth.addr.brick-ns.allow x.x.x.* # Allow access to "brick-ns"
> volume
> end-volume
>
>
> ****Client****
>
> volume brick1
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.102
>  option remote-subvolume brick
> end-volume
>
> volume brick2
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.106
>  option remote-subvolume brick
> end-volume
>
> volume brick3
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.107
>  option remote-subvolume brick
> end-volume
>
> volume brick4
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.103
>  option remote-subvolume brick
> end-volume
>
> volume brick-ns1
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.102
>  option remote-subvolume brick-ns
> end-volume
>
> volume brick-ns2
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.106
>  option remote-subvolume brick-ns
> end-volume
>
> volume brick-ns3
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.107
>  option remote-subvolume brick-ns
> end-volume
>
> volume brick-ns4
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host x.x.x.103
>  option remote-subvolume brick-ns
> end-volume
>
> volume afr1
>  type cluster/afr
>  subvolumes brick1 brick3
> end-volume
>
> volume afr2
>  type cluster/afr
>  subvolumes brick2 brick4
> end-volume
>
> volume afr-ns
>  type cluster/afr
>  subvolumes brick-ns1 brick-ns2 brick-ns3 brick-ns4
> end-volume
>
> volume unify
>  type cluster/unify
>  option namespace afr-ns
>  option scheduler rr
>  subvolumes afr1 afr2
> end-volume
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>




More information about the Gluster-users mailing list