Bug 958574

Description of problem:

After setting up new gluster servers, I wanted to quickly verify a native mount using the private 10g network. Using a system with connectivity on this net, I installed the fuse client.  I attempted to mount the FS using the IP address of one of the servers.  I failed to mount the FS.  Eventually I was able when I put the 10 ghost entries of the cluster servers into the clients fstab.  I did use these names when specify peers.

This brings up several questions:

- Is it better to using IP addresses when specifying peers?
- If not, DNS could be an option, while may be not preferred for a private network.   But what happens if there are DNS errors, does this result in storage errors?
- If additional servers are added to the gluster pool, does this mean the clients need to update their host resolution also?


Version-Release number of selected component (if applicable):

server - 

[root@gprfs038 ~]# cat /etc/redhat-release; uname -a
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Linux gprfs038.sbu.lab.eng.bos.redhat.com 2.6.32-220.34.1.el6.x86_64 #1 SMP Thu Mar 28 19:47:49 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@gprfs038 ~]# yum list installed | grep glusterfs
glusterfs.x86_64                3.3.0.7rhs-1.el6rhs    @anaconda-InstallationRepo-201303202250.x86_64/2.0
glusterfs-fuse.x86_64           3.3.0.7rhs-1.el6rhs    @anaconda-InstallationRepo-201303202250.x86_64/2.0
glusterfs-geo-replication.x86_64
glusterfs-rdma.x86_64           3.3.0.7rhs-1.el6rhs    @anaconda-InstallationRepo-201303202250.x86_64/2.0
glusterfs-server.x86_64         3.3.0.7rhs-1.el6rhs    @anaconda-InstallationRepo-201303202250.x86_64/2.0
org.apache.hadoop.fs.glusterfs-glusterfs.noarch
[root@gprfs038 ~]# 


client - 

[root@gprfc050 ~]# cat /etc/redhat-release ; uname -a
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Linux gprfc050.sbu.lab.eng.bos.redhat.com 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Feb 20 12:17:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@gprfc050 ~]# yum list installed | grep gluster
glusterfs.x86_64                 3.3.0.7rhs-1.el6          @rhel-x86_64-server-rhsclient-6
glusterfs-fuse.x86_64            3.3.0.7rhs-1.el6          @rhel-x86_64-server-rhsclient-6
[root@gprfc050 ~]# 



How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: