[Gluster-users] What was the matter with my GFS 2.0

[Basavanagowda Kanur]

Eagleeyes,
  Please find replies inline.
  Please note that debug messages are harmless.

On Wed, Mar 4, 2009 at 2:34 PM, eagleeyes <eagleeyes at 126.com> wrote:

>  Hello
>     The DEBUG log like this
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option metadata-lock-server-
> count 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option entry-lock-server-cou
> nt 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep-ns: no range check required for 'option data-lock-server-coun
> t 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option metadata-lock-server-co
> unt 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option entry-lock-server-count
>  2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep2: no range check required for 'option data-lock-server-count
> 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option metadata-lock-server-co
> unt 2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option entry-lock-server-count
>  2'
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] rep1: no range check required for 'option data-lock-server-count
> 2'
>
> 2009-03-04 16:16:47 D [client-protocol.c:6221:init] client1: setting transport-timeout to 5
>
> 2009-03-04 16:16:47 D [client-protocol.c:6235:init] client1: defaulting ping-timeout to 10
>
> 2009-03-04 16:16:47 D [transport.c:141:transport_load] transport: attempt to load file /lib/glusterfs/2.0.0rc2/transport/socket.so
>
> 2009-03-04 16:16:47 W [xlator.c:426:validate_xlator_volume_options] client1: option 'transport.socket.remote-port' is deprecated, pr
> eferred is 'remote-port', continuing with correction
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] client1: no range check required for 'option remote-port 6996'
>
> 2009-03-04 16:16:47 D [transport.c:141:transport_load] transport: attempt to load file /lib/glusterfs/2.0.0rc2/transport/socket.so
>
> 2009-03-04 16:16:47 D [xlator.c:154:_volume_option_value_validate] client1: no range check required for 'option remote-port 6996'
>
> 2009-03-04 16:16:47 D [xlator.c:595:xlator_init_rec] client1: Initialization done
>
> " no range check required for " was mean what ? and  the
>
'no range check required for' means that you do not have any limit on
specifying the port numbers.

> option 'transport.socket.remote-port' is deprecated ??
>
'option transport.socket.remote-port <port-number>' is a replacement for
'option remote-port <port-number>'

> Why ? i modify configuration files  use options which   its own .
>
>
>
>
> 2009-03-04
> ------------------------------
>  eagleeyes
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>
>


-- 
Gowda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090311/95a120e1/attachment.html>