volume file of server 1 is as follow:
------------begin -----------
volume brick
type storage/posix
option directory /home/gfs-data
end-volume
volume locks
type features/posix-locks
subvolumes brick
end-volume
volume server
type protocol/server
option transport-type tcp/server
option transport.socket.listen-port 6996
option transport.socket.bind-address 192.168.1.11
subvolumes locks
option auth.addr.brick.allow *
option auth.addr.locks.allow *
end-volume
------------end----------
any mistake in the volume file?
i had noticed the chain, but it still doesn't work. i refered to much
information searched on the internet,but most of then are related to
the older version, and little helpful to solve the problem. im so
puzzled and confused~~~~~
2009/7/13, Jeff Evans <[email protected]>:
> Hi Ling,
>
>> [2009-07-13 11:37:18] W [posix.c:786:init] posix-locks: Volume is
>> dangling. Please check the volume file.
>
> This means that nothing is using your posix-locks, so it won't be
> helping.
> Volume specs are built up in a chain, so don't forget to ensure that
> you also change your server volume definition to utilize additional
> translators that you add in.
>
> Jeff.
>
>
>
>
_______________________________________________
Gluster-users mailing list
[email protected]
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
