On 12/30/2012 02:12 PM, jayunit100 at gmail.com wrote: > The following command > > mount -t glusterfs domU-12-31-39-00-A5-7B:111:PetShop /mnt/petshop Does "mount -t glusterfs domU-12-31-39-00-A5-7B:PetShop /mnt/petshop" work any better? > > fails. Luckily, I found that under /var/log/glusterfs there is a > specific log file for this mount operation: > > It appears that its related to the "port number". > > [root at domU-12-31-39-00-A5-7B ~]# tail /var/log/glusterfs/mnt-petshop.log > [2012-12-30 20:44:17.509907] E > [client-handshake.c:1717:client_query_portmap_cbk] 0-PetShop-client-1: > failed to get the port number for remote subvolume > > I have several questions on this subject: > > 1) How can I know *what port *my gluster server is using? From 3.1 through 3.3, glusterd's management port is 24007/tcp and 24008/tcp if you use rdma. Bricks (glusterfsd) use 24009 & up. (Deleted volumes do not reset this counter.) Additionally it will listen on 38465-38467/tcp for nfs, also 38468 for NLM since 3.3.0. NFS also depends on rpcbind/portmap on port 111. As long as the management port(s) are accessible, you should be able to get the rest of the port information through "gluster volume status". > 2) Can I mount a gluster server as localhost (i.e. > *localhost:PetShop* or 127.0.0.1:PetShop) ? Yes > 3) Is it possible using a command similar to "*gluster volume info*" > to show the *ports* that Bricks are serving on? > Answered above. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121230/03fd8309/attachment.html>
