hi itzik, This looks similar to http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1855 The reason for the bug is that in the 3.1 implementation, the host aliases are not handled properly for localhost. Are you using 3.1 release?. If yes the bug is fixed from http://ftp.gluster.com/pub/gluster/glusterfs/qa-releases/glusterfs-3.1.1qa1.tar.gz Thanks Pranith From: "itzik bar" <kokit74 at yahoo.com> To: "Pranith Kumar. Karampuri" <pranithk at gluster.com> Sent: Thursday, November 11, 2010 3:30:00 PM Subject: Re: Creation of volume has been unsuccessful 127.0.0.1 localhost.localdomain localhost 172.30.47.101 gluster1 172.30.47.102 gluster2 172.30.47.103 gluster3 172.30.47.104 gluster4 I think you can CC. --- On Thu, 11/11/10, Pranith Kumar. Karampuri <pranithk at gluster.com> wrote: From: Pranith Kumar. Karampuri <pranithk at gluster.com> Subject: Re: Creation of volume has been unsuccessful To: "itzik bar" <kokit74 at yahoo.com> Date: Thursday, November 11, 2010, 11:13 AM hi itzik, According to the logs, The DNS resolution of gluster3 on the same machine failed. ======gluster3.log===== [2010-11-10 18:14:07.26112] E [glusterd-op-sm.c:413:glusterd_op_stage_create_volume] glusterd: cannot resolve brick: gluster3:/data1 [2010-11-10 18:14:07.26136] E [glusterd-op-sm.c:4664:glusterd_op_ac_stage_op] : Validate failed: 1 This can happen if the DNS is not setup properly or /etc/hosts files are not setup properly. Could you provide /etc/hosts contents on all these machines to check if they are set up properly? One question: Will it be ok if I CC this thread to gluster-users?. I think it would be helpful for the community to know about issues like these. Thanks Pranith.
