(In reply to fengkun from comment #0)
> Description of problem:
> when i execute replace-brick, always wrong.
> 
> Version-Release number of selected component (if applicable):
> # glusterd -V
> glusterfs 3.5.1 built on Jun 24 2014 15:31:13
> 
> How reproducible:
> command like this:
> gluster volume replace-brick fk 10.96.45.43:/home/brick 
> 10.96.33.20:/home/brick start
> 
> no output anything，view log
> tail -f cli.log 
> [2014-08-18 10:33:23.592596] W [dict.c:1055:data_to_str]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.so(+0x68ec)
> [0x7f892b5108ec]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(socket_client_get_remote_sockaddr+0xad) [0x7f892b514fcd]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(client_fill_address_family+0x20b) [0x7f892b514e8b]))) 0-dict: data is NULL
> [2014-08-18 10:33:23.592602] E [name.c:147:client_fill_address_family]
> 0-glusterfs: transport.address-family not specified. Could not guess default
> value from (remote-host:(null) or transport.unix.connect-path:(null)) options
> [2014-08-18 10:33:26.592787] W [dict.c:1055:data_to_str]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.so(+0x68ec)
> [0x7f892b5108ec]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(socket_client_get_remote_sockaddr+0xad) [0x7f892b514fcd]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(client_fill_address_family+0x200) [0x7f892b514e80]))) 0-dict: data is NULL
> [2014-08-18 10:33:26.592802] W [dict.c:1055:data_to_str]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.so(+0x68ec)
> [0x7f892b5108ec]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(socket_client_get_remote_sockaddr+0xad) [0x7f892b514fcd]
> (-->/usr/lib64/glusterfs/3.5.1/rpc-transport/socket.
> so(client_fill_address_family+0x20b) [0x7f892b514e8b]))) 0-dict: data is NULL
> [2014-08-18 10:33:26.592809] E [name.c:147:client_fill_address_family]
> 0-glusterfs: transport.address-family not specified. Could not guess default
> value from (remote-host:(null) or transport.unix.connect-path:(null)) options
> [2014-08-18 10:33:26.794391] I [input.c:36:cli_batch] 0-: Exiting with: 110

# cat /etc/glusterfs/glusterd.vol 
volume management
    type mgmt/glusterd
    option working-directory /var/lib/glusterd
    option transport-type socket,rdma
    option transport.socket.keepalive-time 10
    option transport.socket.keepalive-interval 2
    option transport.socket.read-fail-log off
#   option base-port 49152
    option rpc-auth-allow-insecure on
    option transport.address-family inet
end-volume

Can you please give us more details about the volume configuration you have and the exact snip of actions you performed ?

(In reply to Humble Chirammal from comment #3)
> Can you please give us more details about the volume configuration you have
> and the exact snip of actions you performed ?

use yum, The default installation,The default configuration

(In reply to fengkun from comment #4)
> (In reply to Humble Chirammal from comment #3)
> > Can you please give us more details about the volume configuration you have
> > and the exact snip of actions you performed ?
> 
> use yum, The default installation,The default configuration

By 'Volume configuration' I mean , your gluster volume configuration ( distribute, distribute-replice..etc)  which can be retrieved by #gluster volume info command. Also I would like to know why this action is performed, that said, is it for replacing a faulty disk or to expand some space in your configuration ?

All replace-brick commands except commit force are deprecated. The gluster cli itself will warn you about this from next versions.

(In reply to Humble Chirammal from comment #5)
> (In reply to fengkun from comment #4)
> > (In reply to Humble Chirammal from comment #3)
> > > Can you please give us more details about the volume configuration you have
> > > and the exact snip of actions you performed ?
> > 
> > use yum, The default installation,The default configuration
> 
> By 'Volume configuration' I mean , your gluster volume configuration (
> distribute, distribute-replice..etc)  which can be retrieved by #gluster
> volume info command. Also I would like to know why this action is performed,
> that said, is it for replacing a faulty disk or to expand some space in your
> configuration ?
> 
> All replace-brick commands except commit force are deprecated. The gluster
> cli itself will warn you about this from next versions.

You can refer below doc  for the same.
http://review.gluster.org/#/c/8503/

Was your problem resolved with the hints in comment #6? If not, could you explain with a clear example what you are doing, and when this problem occurs?

its seems problem have solved. closing this bug.

fengkun feel free to raise the issue if you face the same problem.