Hi David, as requested, Thanks, Steve
[root@nas-0-0 ~]# lsof -n | grep 24007 glusterd 7943 root 6u IPv4 468358 0t0 TCP 127.0.0.1:24007->127.0.0.1:1021 (ESTABLISHED) glusterd 7943 root 8u IPv4 402704 0t0 TCP *:24007 (LISTEN) glusterd 7943 root 10u IPv4 472454 0t0 TCP 10.1.1.10:1022->10.0.0.11:24007 (SYN_SENT) glusterd 7943 root 12u IPv4 468316 0t0 TCP 10.1.1.10:1023->10.0.0.2:24007 (ESTABLISHED) glusterfs 7965 root 7u IPv4 468357 0t0 TCP 127.0.0.1:1021->127.0.0.1:24007 (ESTABLISHED) glusterfs 7965 root 16u IPv4 472450 0t0 TCP 10.1.1.10:1020->10.0.0.10:24007 (SYN_SENT) [root@nas-0-0 ~]# lsof -n | grep 24009 glusterfs 7965 root 18u IPv4 468428 0t0 TCP 10.1.1.10:1021->10.0.0.2:24009 (ESTABLISHED) [root@nas-0-0 ~]# lsof -n | grep 24010 [root@nas-0-0 ~]# lsof -n | grep 24011 [root@nas-0-0 ~]# [root@nas-0-1 ~]# lsof -n | grep 24007 glusterd 7567 root 6u IPv4 388277 0t0 TCP 127.0.0.1:24007->127.0.0.1:1021 (ESTABLISHED) glusterd 7567 root 8u IPv4 322628 0t0 TCP *:24007 (LISTEN) glusterd 7567 root 12u IPv4 388240 0t0 TCP 10.1.1.11:1023->10.0.0.2:24007 (ESTABLISHED) glusterfs 7589 root 7u IPv4 388276 0t0 TCP 127.0.0.1:1021->127.0.0.1:24007 (ESTABLISHED) glusterfs 7589 root 17u IPv4 392099 0t0 TCP 10.1.1.11:1019->10.0.0.11:24007 (SYN_SENT) [root@nas-0-1 ~]# lsof -n | grep 24009 glusterfs 7589 root 18u IPv4 388347 0t0 TCP 10.1.1.11:1021->10.0.0.2:24009 (ESTABLISHED) [root@nas-0-1 ~]# lsof -n | grep 24010 [root@nas-0-1 ~]# lsof -n | grep 24011 [root@nas-0-1 ~]# [root@mseas-data ~]# lsof -n | grep 24007 glusterd 22582 root 6u IPv4 664645 TCP 127.0.0.1:24007->127.0.0.1:1021 (ESTABLISHED) glusterd 22582 root 8u IPv4 598942 TCP *:24007 (LISTEN) glusterd 22582 root 10u IPv4 664647 TCP 127.0.0.1:24007->127.0.0.1:1020 (ESTABLISHED) glusterd 22582 root 15u IPv4 664723 TCP 18.38.1.23:24007->10.1.255.240:1023 (ESTABLISHED) glusterd 22582 root 16u IPv4 664725 TCP 18.38.1.23:24007->10.1.255.175:1023 (ESTABLISHED) glusterd 22582 root 17u IPv4 664726 TCP 18.38.1.23:24007->10.1.255.160:1023 (ESTABLISHED) glusterd 22582 root 18u IPv4 664727 TCP 18.38.1.23:24007->10.1.255.189:1023 (ESTABLISHED) glusterd 22582 root 19u IPv4 664728 TCP 18.38.1.23:24007->10.1.255.188:1023 (ESTABLISHED) glusterd 22582 root 20u IPv4 664729 TCP 18.38.1.23:24007->10.1.255.203:1023 (ESTABLISHED) glusterd 22582 root 21u IPv4 664731 TCP 18.38.1.23:24007->10.1.255.197:1023 (ESTABLISHED) glusterd 22582 root 22u IPv4 664733 TCP 18.38.1.23:24007->10.1.255.157:1023 (ESTABLISHED) glusterd 22582 root 23u IPv4 664734 TCP 18.38.1.23:24007->10.1.255.186:1023 (ESTABLISHED) glusterd 22582 root 24u IPv4 664735 TCP 18.38.1.23:24007->10.1.255.130:1023 (ESTABLISHED) glusterd 22582 root 25u IPv4 664737 TCP 18.38.1.23:24007->10.1.255.211:1023 (ESTABLISHED) glusterd 22582 root 26u IPv4 664738 TCP 18.38.1.23:24007->10.1.255.150:1023 (ESTABLISHED) glusterd 22582 root 27u IPv4 664740 TCP 18.38.1.23:24007->10.1.255.168:1023 (ESTABLISHED) glusterd 22582 root 28u IPv4 664741 TCP 18.38.1.23:24007->10.1.255.215:1023 (ESTABLISHED) glusterd 22582 root 29u IPv4 664742 TCP 18.38.1.23:24007->10.1.255.208:1023 (ESTABLISHED) glusterd 22582 root 30u IPv4 664743 TCP 18.38.1.23:24007->10.1.255.164:1023 (ESTABLISHED) glusterd 22582 root 31u IPv4 664744 TCP 18.38.1.23:24007->10.1.255.156:1023 (ESTABLISHED) glusterd 22582 root 32u IPv4 664745 TCP 18.38.1.23:24007->10.1.255.236:1023 (ESTABLISHED) glusterd 22582 root 33u IPv4 664746 TCP 18.38.1.23:24007->10.1.255.193:1023 (ESTABLISHED) glusterd 22582 root 34u IPv4 664747 TCP 18.38.1.23:24007->10.1.255.217:1023 (ESTABLISHED) glusterd 22582 root 35u IPv4 664749 TCP 18.38.1.23:24007->10.1.255.228:1023 (ESTABLISHED) glusterd 22582 root 36u IPv4 664750 TCP 18.38.1.23:24007->10.1.255.202:1023 (ESTABLISHED) glusterd 22582 root 37u IPv4 664751 TCP 18.38.1.23:24007->10.1.255.190:1023 (ESTABLISHED) glusterd 22582 root 38u IPv4 664752 TCP 18.38.1.23:24007->10.1.255.163:1023 (ESTABLISHED) glusterd 22582 root 39u IPv4 664753 TCP 18.38.1.23:24007->10.1.255.198:1023 (ESTABLISHED) glusterd 22582 root 40u IPv4 664754 TCP 18.38.1.23:24007->10.1.255.206:1023 (ESTABLISHED) glusterd 22582 root 41u IPv4 664755 TCP 18.38.1.23:24007->10.1.255.142:1023 (ESTABLISHED) glusterd 22582 root 42u IPv4 664756 TCP 18.38.1.23:24007->10.1.255.253:1023 (ESTABLISHED) glusterd 22582 root 43u IPv4 664757 TCP 18.38.1.23:24007->10.1.255.221:1023 (ESTABLISHED) glusterd 22582 root 44u IPv4 664758 TCP 18.38.1.23:24007->10.1.255.200:1023 (ESTABLISHED) glusterd 22582 root 45u IPv4 664760 TCP 18.38.1.23:24007->10.1.255.162:1023 (ESTABLISHED) glusterd 22582 root 46u IPv4 664761 TCP 18.38.1.23:24007->10.1.255.191:1023 (ESTABLISHED) glusterd 22582 root 47u IPv4 664762 TCP 18.38.1.23:24007->10.1.255.169:1023 (ESTABLISHED) glusterd 22582 root 48u IPv4 664764 TCP 18.38.1.23:24007->10.1.255.229:1023 (ESTABLISHED) glusterd 22582 root 49u IPv4 664765 TCP 18.38.1.23:24007->10.1.255.176:1023 (ESTABLISHED) glusterd 22582 root 50u IPv4 664766 TCP 18.38.1.23:24007->10.1.255.194:1023 (ESTABLISHED) glusterd 22582 root 51u IPv4 664767 TCP 18.38.1.23:24007->10.1.255.249:1023 (ESTABLISHED) glusterd 22582 root 52u IPv4 664768 TCP 18.38.1.23:24007->10.1.255.205:1023 (ESTABLISHED) glusterd 22582 root 53u IPv4 664769 TCP 18.38.1.23:24007->10.1.255.124:1023 (ESTABLISHED) glusterd 22582 root 54u IPv4 664770 TCP 18.38.1.23:24007->10.1.255.201:1023 (ESTABLISHED) glusterd 22582 root 55u IPv4 664771 TCP 18.38.1.23:24007->10.1.255.182:1023 (ESTABLISHED) glusterd 22582 root 56u IPv4 664772 TCP 18.38.1.23:24007->10.1.255.148:1023 (ESTABLISHED) glusterd 22582 root 57u IPv4 664774 TCP 18.38.1.23:24007->10.1.255.226:1023 (ESTABLISHED) glusterd 22582 root 58u IPv4 664775 TCP 18.38.1.23:24007->10.1.255.154:1023 (ESTABLISHED) glusterd 22582 root 59u IPv4 664776 TCP 18.38.1.23:24007->10.1.255.238:1023 (ESTABLISHED) glusterd 22582 root 60u IPv4 664777 TCP 18.38.1.23:24007->10.1.255.171:1023 (ESTABLISHED) glusterd 22582 root 61u IPv4 664778 TCP 18.38.1.23:24007->10.1.255.146:1023 (ESTABLISHED) glusterd 22582 root 62u IPv4 664779 TCP 18.38.1.23:24007->10.1.255.232:1023 (ESTABLISHED) glusterd 22582 root 63u IPv4 664780 TCP 18.38.1.23:24007->10.1.255.143:1023 (ESTABLISHED) glusterd 22582 root 64u IPv4 664781 TCP 18.38.1.23:24007->10.1.255.218:1023 (ESTABLISHED) glusterd 22582 root 65u IPv4 664783 TCP 18.38.1.23:24007->10.1.255.144:1023 (ESTABLISHED) glusterd 22582 root 66u IPv4 664784 TCP 18.38.1.23:24007->10.1.255.123:1023 (ESTABLISHED) glusterd 22582 root 67u IPv4 664785 TCP 18.38.1.23:24007->10.1.255.235:1023 (ESTABLISHED) glusterd 22582 root 68u IPv4 664787 TCP 18.38.1.23:24007->10.1.255.147:1023 (ESTABLISHED) glusterd 22582 root 69u IPv4 664788 TCP 18.38.1.23:24007->10.1.255.230:1023 (ESTABLISHED) glusterd 22582 root 70u IPv4 664789 TCP 18.38.1.23:24007->10.1.255.223:1023 (ESTABLISHED) glusterd 22582 root 71u IPv4 664790 TCP 18.38.1.23:24007->10.1.255.133:1023 (ESTABLISHED) glusterd 22582 root 72u IPv4 664792 TCP 18.38.1.23:24007->10.1.255.192:1023 (ESTABLISHED) glusterd 22582 root 73u IPv4 664793 TCP 18.38.1.23:24007->10.1.255.155:1023 (ESTABLISHED) glusterd 22582 root 74u IPv4 664794 TCP 18.38.1.23:24007->10.1.255.209:1023 (ESTABLISHED) glusterd 22582 root 75u IPv4 664795 TCP 18.38.1.23:24007->10.1.255.187:1023 (ESTABLISHED) glusterd 22582 root 76u IPv4 664796 TCP 18.38.1.23:24007->10.1.255.210:1023 (ESTABLISHED) glusterd 22582 root 77u IPv4 664797 TCP 18.38.1.23:24007->10.1.255.212:1023 (ESTABLISHED) glusterd 22582 root 78u IPv4 664799 TCP 18.38.1.23:24007->10.1.255.173:1023 (ESTABLISHED) glusterd 22582 root 79u IPv4 664800 TCP 18.38.1.23:24007->10.1.255.159:1023 (ESTABLISHED) glusterd 22582 root 80u IPv4 664801 TCP 18.38.1.23:24007->10.1.255.220:1023 (ESTABLISHED) glusterd 22582 root 81u IPv4 664802 TCP 18.38.1.23:24007->10.1.255.167:1023 (ESTABLISHED) glusterd 22582 root 82u IPv4 664803 TCP 18.38.1.23:24007->10.1.255.234:1023 (ESTABLISHED) glusterd 22582 root 83u IPv4 664804 TCP 18.38.1.23:24007->10.1.255.214:1023 (ESTABLISHED) glusterd 22582 root 84u IPv4 664805 TCP 18.38.1.23:24007->10.1.255.151:1023 (ESTABLISHED) glusterd 22582 root 85u IPv4 664807 TCP 18.38.1.23:24007->10.1.255.243:1023 (ESTABLISHED) glusterd 22582 root 86u IPv4 664808 TCP 18.38.1.23:24007->10.1.255.129:1023 (ESTABLISHED) glusterd 22582 root 87u IPv4 664811 TCP 18.38.1.23:24007->10.1.255.252:1023 (ESTABLISHED) glusterd 22582 root 88u IPv4 664812 TCP 18.38.1.23:24007->10.1.255.174:1023 (ESTABLISHED) glusterd 22582 root 89u IPv4 664813 TCP 18.38.1.23:24007->10.1.255.149:1023 (ESTABLISHED) glusterd 22582 root 90u IPv4 664814 TCP 18.38.1.23:24007->10.1.255.239:1023 (ESTABLISHED) glusterd 22582 root 91u IPv4 664815 TCP 18.38.1.23:24007->10.1.255.158:1023 (ESTABLISHED) glusterd 22582 root 92u IPv4 664817 TCP 18.38.1.23:24007->10.1.255.195:1023 (ESTABLISHED) glusterd 22582 root 93u IPv4 664818 TCP 18.38.1.23:24007->10.1.255.244:1023 (ESTABLISHED) glusterd 22582 root 94u IPv4 664819 TCP 18.38.1.23:24007->10.1.255.242:1023 (ESTABLISHED) glusterd 22582 root 95u IPv4 664821 TCP 18.38.1.23:24007->10.1.255.181:1023 (ESTABLISHED) glusterd 22582 root 96u IPv4 664822 TCP 18.38.1.23:24007->10.1.255.165:1023 (ESTABLISHED) glusterd 22582 root 97u IPv4 664823 TCP 18.38.1.23:24007->10.1.255.145:1023 (ESTABLISHED) glusterd 22582 root 98u IPv4 664825 TCP 18.38.1.23:24007->10.1.255.179:1023 (ESTABLISHED) glusterd 22582 root 99u IPv4 664826 TCP 18.38.1.23:24007->10.1.255.183:1023 (ESTABLISHED) glusterd 22582 root 100u IPv4 664827 TCP 18.38.1.23:24007->10.1.255.199:1023 (ESTABLISHED) glusterd 22582 root 101u IPv4 664829 TCP 18.38.1.23:24007->10.1.255.172:1023 (ESTABLISHED) glusterd 22582 root 102u IPv4 664830 TCP 18.38.1.23:24007->10.1.255.247:1023 (ESTABLISHED) glusterd 22582 root 103u IPv4 664841 TCP 18.38.1.23:24007->10.1.255.185:1023 (ESTABLISHED) glusterd 22582 root 104u IPv4 664843 TCP 18.38.1.23:24007->10.1.255.131:1023 (ESTABLISHED) glusterd 22582 root 105u IPv4 664844 TCP 18.38.1.23:24007->10.1.255.233:1023 (ESTABLISHED) glusterd 22582 root 106u IPv4 664845 TCP 18.38.1.23:24007->10.1.255.251:1023 (ESTABLISHED) glusterd 22582 root 107u IPv4 664847 TCP 18.38.1.23:24007->10.1.255.184:1023 (ESTABLISHED) glusterd 22582 root 108u IPv4 664849 TCP 18.38.1.23:24007->10.1.255.132:1023 (ESTABLISHED) glusterd 22582 root 109u IPv4 664851 TCP 18.38.1.23:24007->10.1.255.216:1023 (ESTABLISHED) glusterd 22582 root 110u IPv4 664853 TCP 18.38.1.23:24007->10.1.255.237:1023 (ESTABLISHED) glusterd 22582 root 111u IPv4 664854 TCP 18.38.1.23:24007->10.1.255.127:1023 (ESTABLISHED) glusterd 22582 root 112u IPv4 664855 TCP 18.38.1.23:24007->10.1.255.128:1023 (ESTABLISHED) glusterd 22582 root 113u IPv4 664856 TCP 18.38.1.23:24007->10.1.255.222:1023 (ESTABLISHED) glusterd 22582 root 114u IPv4 664858 TCP 18.38.1.23:24007->10.1.255.141:1023 (ESTABLISHED) glusterd 22582 root 115u IPv4 664859 TCP 18.38.1.23:24007->10.1.255.178:1023 (ESTABLISHED) glusterd 22582 root 116u IPv4 664860 TCP 18.38.1.23:24007->10.1.255.152:1023 (ESTABLISHED) glusterd 22582 root 117u IPv4 664861 TCP 18.38.1.23:24007->10.1.255.231:1023 (ESTABLISHED) glusterd 22582 root 118u IPv4 664862 TCP 18.38.1.23:24007->10.1.255.134:1023 (ESTABLISHED) glusterd 22582 root 119u IPv4 664863 TCP 18.38.1.23:24007->10.1.255.224:1023 (ESTABLISHED) glusterd 22582 root 120u IPv4 664865 TCP 18.38.1.23:24007->10.1.255.248:1023 (ESTABLISHED) glusterd 22582 root 121u IPv4 664866 TCP 18.38.1.23:24007->10.1.255.161:1023 (ESTABLISHED) glusterd 22582 root 122u IPv4 664867 TCP 18.38.1.23:24007->10.1.255.177:1023 (ESTABLISHED) glusterd 22582 root 123u IPv4 664868 TCP 18.38.1.23:24007->10.1.255.170:1023 (ESTABLISHED) glusterd 22582 root 124u IPv4 664869 TCP 18.38.1.23:24007->10.1.255.241:1023 (ESTABLISHED) glusterd 22582 root 125u IPv4 664870 TCP 18.38.1.23:24007->10.1.255.254:1023 (ESTABLISHED) glusterd 22582 root 126u IPv4 664871 TCP 18.38.1.23:24007->10.1.255.135:1023 (ESTABLISHED) glusterd 22582 root 127u IPv4 664872 TCP 18.38.1.23:24007->10.1.255.250:1023 (ESTABLISHED) glusterd 22582 root 128u IPv4 664873 TCP 18.38.1.23:24007->10.1.255.196:1023 (ESTABLISHED) glusterd 22582 root 129u IPv4 664874 TCP 18.38.1.23:24007->10.1.255.207:1023 (ESTABLISHED) glusterd 22582 root 130u IPv4 664876 TCP 18.38.1.23:24007->10.1.255.166:1023 (ESTABLISHED) glusterd 22582 root 131u IPv4 664877 TCP 18.38.1.23:24007->10.1.255.153:1023 (ESTABLISHED) glusterd 22582 root 132u IPv4 664878 TCP 18.38.1.23:24007->10.1.255.213:1023 (ESTABLISHED) glusterd 22582 root 133u IPv4 664879 TCP 18.38.1.23:24007->10.1.255.219:1023 (ESTABLISHED) glusterd 22582 root 134u IPv4 664881 TCP 18.38.1.23:24007->10.1.255.180:1023 (ESTABLISHED) glusterd 22582 root 135u IPv4 664882 TCP 18.38.1.23:24007->10.1.255.204:1023 (ESTABLISHED) glusterd 22582 root 136u IPv4 664883 TCP 18.38.1.23:24007->10.1.255.225:1023 (ESTABLISHED) glusterd 22582 root 137u IPv4 664884 TCP 18.38.1.23:24007->10.1.255.227:1023 (ESTABLISHED) glusterd 22582 root 138u IPv4 664886 TCP 18.38.1.23:24007->10.1.255.246:1023 (ESTABLISHED) glusterd 22582 root 139u IPv4 664898 TCP 18.38.1.23:24007->10.1.255.245:1023 (ESTABLISHED) glusterd 22582 root 141u IPv4 666862 TCP 10.0.0.2:24007->10.1.1.10:1023 (ESTABLISHED) glusterd 22582 root 142u IPv4 670639 TCP 10.0.0.2:24007->10.1.1.11:1023 (ESTABLISHED) glusterfs 22603 root 7u IPv4 664633 TCP 127.0.0.1:1021->127.0.0.1:24007 (ESTABLISHED) glusterfs 22609 root 7u IPv4 664643 TCP 127.0.0.1:1020->127.0.0.1:24007 (ESTABLISHED) [root@mseas-data ~]# lsof -n | grep 24009 glusterfs 22603 root 10u IPv4 664658 TCP *:24009 (LISTEN) glusterfs 22603 root 13u IPv4 665090 TCP 10.0.0.2:24009->10.0.0.2:1022 (ESTABLISHED) glusterfs 22603 root 14u IPv4 667011 TCP 10.0.0.2:24009->10.1.1.10:1021 (ESTABLISHED) glusterfs 22603 root 15u IPv4 670783 TCP 10.0.0.2:24009->10.1.1.11:1021 (ESTABLISHED) glusterfs 22609 root 18u IPv4 665089 TCP 10.0.0.2:1022->10.0.0.2:24009 (ESTABLISHED) [root@mseas-data ~]# lsof -n | grep 24010 [root@mseas-data ~]# lsof -n | grep 24011 [root@mseas-data ~]# ________________________________ From: David Coulson [[email protected]] Sent: Wednesday, November 21, 2012 3:20 PM To: Steve Postma Cc: Eco Willson; [email protected] Subject: Re: [Gluster-users] FW: cant mount gluster volume I would be concerned about the connections in a SYN_SENT state. Would be helpful if this was done with the -n flag so no DNS and we could see the real IPs. On 11/21/12 2:49 PM, Steve Postma wrote: > Eco, > they all appear to be using 24007 and 24009, none of them are running on > 24010 or 24011. > Steve > > [root@nas-0-0<mailto:root@nas-0-0> ~]# lsof | grep 24010 > [root@nas-0-0<mailto:root@nas-0-0> ~]# lsof | grep 24011 > [root@nas-0-0<mailto:root@nas-0-0> ~]# lsof | grep 24009 > glusterfs 3536 root 18u IPv4 143541 0t0 TCP > 10.1.1.10:1022->gluster-data:24009 (ESTABLISHED) > [root@nas-0-0<mailto:root@nas-0-0> ~]# lsof | grep 24007 > glusterd 3515 root 6u IPv4 143469 0t0 TCP nas-0-0:24007->nas-0-0:1022 > (ESTABLISHED) > glusterd 3515 root 8u IPv4 77801 0t0 TCP *:24007 (LISTEN) > glusterd 3515 root 12u IPv4 143805 0t0 TCP 10.1.1.10:1020->gluster-data:24007 > (ESTABLISHED) > glusterfs 3536 root 7u IPv4 143468 0t0 TCP nas-0-0:1022->nas-0-0:24007 > (ESTABLISHED) > glusterfs 3536 root 16u IPv4 399743 0t0 TCP 10.1.1.10:1023->gluster-0-0:24007 > (SYN_SENT) > glusterfs 3536 root 17u IPv4 399745 0t0 TCP 10.1.1.10:1021->gluster-0-1:24007 > (SYN_SENT) > > > > [root@nas-0-1<mailto:root@nas-0-1> ~]# lsof | grep 24007 > glusterd 3447 root 6u IPv4 77189 0t0 TCP nas-0-1:24007->nas-0-1:1021 > (ESTABLISHED) > glusterd 3447 root 8u IPv4 11540 0t0 TCP *:24007 (LISTEN) > glusterd 3447 root 10u IPv4 317363 0t0 TCP 10.1.1.11:1022->gluster-0-0:24007 > (SYN_SENT) > glusterd 3447 root 12u IPv4 77499 0t0 TCP 10.1.1.11:1023->gluster-data:24007 > (ESTABLISHED) > glusterfs 3468 root 7u IPv4 77188 0t0 TCP nas-0-1:1021->nas-0-1:24007 > (ESTABLISHED) > glusterfs 3468 root 17u IPv4 317361 0t0 TCP 10.1.1.11:1019->gluster-0-1:24007 > (SYN_SENT) > [root@nas-0-1<mailto:root@nas-0-1> ~]# lsof | grep 24009 > glusterfs 3468 root 18u IPv4 77259 0t0 TCP 10.1.1.11:1021->gluster-data:24009 > (ESTABLISHED) > [root@nas-0-1<mailto:root@nas-0-1> ~]# lsof | grep 24010 > [root@nas-0-1<mailto:root@nas-0-1> ~]# lsof | grep 24011 > > glusterfs 4301 root 16u IPv4 586766 TCP 10.1.1.2:1021->gluster-0-0:24007 > (SYN_SENT) > glusterfs 4301 root 17u IPv4 586768 TCP 10.1.1.2:1020->gluster-0-1:24007 > (SYN_SENT) > glusterfs 17526 root 8u IPv4 205563 TCP > mseas-data.mit.edu:1015->mseas-data.mit.edu:24007 (ESTABLISHED) > [root@mseas-data<mailto:root@mseas-data> ~]# lsof | grep 24009 > glusterfs 4008 root 10u IPv4 77692 TCP *:24009 (LISTEN) > glusterfs 4008 root 13u IPv4 148473 TCP gluster-data:24009->gluster-data:1018 > (ESTABLISHED) > glusterfs 4008 root 14u IPv4 82251 TCP gluster-data:24009->10.1.1.10:1022 > (ESTABLISHED) > glusterfs 4008 root 15u IPv4 82440 TCP gluster-data:24009->10.1.1.11:1021 > (ESTABLISHED) > glusterfs 4008 root 16u IPv4 205600 TCP gluster-data:24009->gluster-data:1023 > (ESTABLISHED) > glusterfs 4008 root 17u IPv4 218671 TCP 10.1.1.2:24009->10.1.1.1:1018 > (ESTABLISHED) > glusterfs 4301 root 18u IPv4 148472 TCP gluster-data:1018->gluster-data:24009 > (ESTABLISHED) > glusterfs 17526 root 12u IPv4 205599 TCP > gluster-data:1023->gluster-data:24009 (ESTABLISHED) > [root@mseas-data<mailto:root@mseas-data> ~]# lsof | grep 24010 > [root@mseas-data<mailto:root@mseas-data> ~]# lsof | grep 24011 > [root@mseas-data<mailto:root@mseas-data> ~]# > > > > ________________________________ > From: > [email protected]<mailto:[email protected]> > [[email protected]<mailto:[email protected]>] > on behalf of Steve Postma [[email protected]<mailto:[email protected]>] > Sent: Wednesday, November 21, 2012 10:19 AM > To: Eco Willson; [email protected]<mailto:[email protected]> > Subject: Re: [Gluster-users] FW: cant mount gluster volume > > Your right Eco > I am only able to telnet on port 24007, ports 24009, 24010 and 24011 are all > connection refused . Iptables is not running on any of the machines > > > mseas-data 24007, 24009 are open, 24010 and 24011 closed > nas-0-0 24007 open, 24009,24010 and 24011 closed > nas-0-1 24007 open, 24009,24010 and 24011 closed > > > > Steve > ________________________________ > From: > [email protected]<mailto:[email protected]><mailto:[email protected]> > > [[email protected]<mailto:[email protected]><mailto:[email protected]>] > on behalf of Eco Willson > [[email protected]<mailto:[email protected]><mailto:[email protected]>] > Sent: Tuesday, November 20, 2012 6:32 PM > To: > [email protected]<mailto:[email protected]><mailto:[email protected]> > Subject: Re: [Gluster-users] FW: cant mount gluster volume > > Steve, > On 11/20/2012 02:43 PM, Steve Postma wrote: >> Hi Eco, >> I believe you are asking that I run >> >> find /mount/glusterfs >/dev/null >> >> only? That should take care of the issue? > Meaning, run a recursive find against the client mount point > (/mount/glusterfs is used as an example in the docs). This should solve > the specific issue of the files not being visible. > However, the issue of the disk space discrepancy is different. From the > df output, the only filesystem with 18GB is / on the mseas-data node, I > assume this is where you are mounting from? > If so, then the issue goes back to one of connectivity, the gluster > bricks most likely are still not being connected to, which may actually > be the root cause of both problems. > > Can you confirm that iptables is off on all hosts (and from any client > you would connect from)? I had seen your previous tests with telnet, > was this done from and to all hosts from the client machine? > Make sure that at a minimum you can hit 24007, 24009, 24010 and 24011. > This will test the management port and the expected initial port for > each of the bricks in the volume. > > > Thanks, > > Eco > >> Thanks for your time, >> Steve >> >> ________________________________ >> From: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> on behalf of Eco Willson >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> Sent: Tuesday, November 20, 2012 5:39 PM >> To: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> Subject: Re: [Gluster-users] FW: cant mount gluster volume >> >> Steve, >> >> On 11/20/2012 01:32 PM, Steve Postma wrote: >> >> [root@mseas-data<mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data> >> gdata]# df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda1 18G 6.6G 9.7G 41% / >> /dev/sda6 77G 49G 25G 67% /scratch >> /dev/sda3 18G 3.8G 13G 24% /var >> /dev/sda2 18G 173M 16G 2% /tmp >> tmpfs 3.9G 0 3.9G 0% /dev/shm >> /dev/mapper/the_raid-lv_home >> 3.0T 2.2T 628G 79% /home >> glusterfs#mseas-data:/gdata >> 15T 14T 606G 96% /gdata >> >> >> [root@nas-0-0<mailto:root@nas-0-0><mailto:root@nas-0-0><mailto:root@nas-0-0> >> ~]# df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda3 137G 33G 97G 26% / >> /dev/sda1 190M 24M 157M 14% /boot >> tmpfs 2.0G 0 2.0G 0% /dev/shm >> /dev/sdb1 21T 19T 1.5T 93% /mseas-data-0-0 >> >> [root@nas-0-1<mailto:root@nas-0-1><mailto:root@nas-0-1><mailto:root@nas-0-1> >> ~]# df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda3 137G 34G 97G 26% / >> /dev/sda1 190M 24M 157M 14% /boot >> tmpfs 2.0G 0 2.0G 0% /dev/shm >> /dev/sdb1 21T 19T 1.3T 94% /mseas-data-0-1 >> >> >> Thanks for confirming. >> >> cat of /etc/glusterfs/glusterd.vol from backup >> >> [root@mseas-data<mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data> >> glusterd]# cat /root/mseas_backup/etc/glusterfs/glusterd.vol >> volume management >> type mgmt/glusterd >> option working-directory /etc/glusterd >> option transport-type socket,rdma >> option transport.socket.keepalive-time 10 >> option transport.socket.keepalive-interval 2 >> end-volume >> >> >> The vol file for 2.x would be in /etc/glusterfs/<volume name>.vol I believe. >> It should contain an entry similar to this output for each of the servers >> toward the top of the file. >> >> Article you referenced is looking for the words "glusterfs-volgen" in a vol >> file. I have used locate and grep, but can find no such entry in any .vol >> files. >> >> >> This would not appear if the glusterfs-volgen command wasn't used during >> creation. The main consideration is to ensure that you have the command in >> step 5: >> >> find /mount/glusterfs >/dev/null >> >> - Eco >> >> Thanks >> >> >> >> >> ________________________________ >> From: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> on behalf of Eco Willson >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> Sent: Tuesday, November 20, 2012 4:03 PM >> To: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> Subject: Re: [Gluster-users] FW: cant mount gluster volume >> >> Steve, >> >> >> >> On 11/20/2012 12:03 PM, Steve Postma wrote: >> >> >> The do show expected size. I have a backup of /etc/glusterd and >> /etc/glusterfs from before upgrade. >> >> >> Can we see the vol file from the 2.x install and the output of df -h for >> each of the bricks? >> >> >> Its interesting that "gluster volume info" shows the correct path for each >> machine. >> >> These are the correct mountpoints on each machine, and from each machine I >> can see the files and structure. >> >> >> If the volume was created in a different order than before, then it is >> expected you would be able to see the files only from the backend >> directories and not from the client mount. >> If this is the case, recreating the volume in the correct order should >> show the files from the mount. >> If the volume was recreated properly, make sure you have followed the >> upgrade steps to go from versions prior to 3.1: >> http://www.gluster.org/community/documentation/index.php/Gluster_3.0_to_3.2_Upgrade_Guide >> >> This would explain why the files can't be viewed from the client, but >> the size discrepancy isn't expected if we see the expected output from >> df for the bricks. >> >> >> >> >> [root@mseas-data<mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data> >> data]# gluster volume info >> >> Volume Name: gdata >> Type: Distribute >> Volume ID: eccc3a90-212d-4563-ae8d-10a77758738d >> Status: Started >> Number of Bricks: 3 >> Transport-type: tcp >> Bricks: >> Brick1: gluster-0-0:/mseas-data-0-0 >> Brick2: gluster-0-1:/mseas-data-0-1 >> Brick3: gluster-data:/data >> >> >> >> ________________________________ >> From: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> on behalf of Eco Willson >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> Sent: Tuesday, November 20, 2012 3:02 PM >> To: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> Subject: Re: [Gluster-users] FW: cant mount gluster volume >> >> Steve, >> >> >> >> >> Does df -h show the expected directories on each server, and do they >> show the expected size? >> >> If the file >> >> >> On 11/20/2012 11:09 AM, Steve Postma wrote: >> >> >> Hi Eco, thanks for your help. >> >> If I run on brick 1: >> mount -t glusterfs gluster-data:/gdata /gdata >> >> it mounts but appears as a 18 GB partition with nothing in it >> >> >> To confirm, are the export directories mounted properly on all three >> servers? >> Does df -h show the expected directories on each server, and do they >> show the expected size? >> Does gluster volume info show the same output on all three servers? >> >> >> I can mount it from the client, but again, there is nothing in it. >> >> >> >> Before upgrade this was a 50 TB gluster volume. Was that volume information >> lost with upgrade? >> >> >> Do you have the old vol files from before the upgrade? It would be good >> to see them to make sure the volume got recreated properly. >> >> >> The file structure appears intact on each brick. >> >> >> As long as the file structure is intact, you will be able to recreate >> the volume although it may require a potentially painful rsync in the >> worst case. >> >> - Eco >> >> >> >> >> >> Steve >> >> >> ________________________________ >> From: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> on behalf of Eco Willson >> [[email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:ewillson! >> @redhat.co >> m><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]>] >> Sent: Tuesday, November 20, 2012 1:29 PM >> To: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> Subject: Re: [Gluster-users] FW: cant mount gluster volume >> >> Steve, >> >> The volume is a pure distribute: >> >> >> >> Type: Distribute >> >> >> In order to have files replicate, you need >> 1) to have a number of bricks that is a multiple of the replica count, >> e.g., for your three node configuration, you would need two bricks per >> node to set up replica two. You could set up replica 3, but you will >> take a performance hit in doing so. >> 2) to add a replica count during the volume creation, e.g. >> `gluster volume create <vol name> replica 2 server1:/export server2:/export >> >> From the volume info you provided, the export directories are different >> for all three nodes: >> >> Brick1: gluster-0-0:/mseas-data-0-0 >> Brick2: gluster-0-1:/mseas-data-0-1 >> Brick3: gluster-data:/data >> >> >> Which node are you trying to mount to /data? If it is not the >> gluster-data node, then it will fail if there is not a /data directory. >> In this case, it is a good thing, since mounting to /data on gluster-0-0 >> or gluster-0-1 would not accomplish what you need. >> To clarify, there is a distinction to be made between the export volume >> mount and the gluster mount point. In this case, you are mounting the >> brick. >> In order to see all the files, you would need to mount the volume with >> the native client, or NFS. >> For the native client: >> mount -t glusterfs gluster-data:/gdata /mnt/<gluster mount dir> >> For NFS: >> mount -t nfs -o vers=3 gluster-data:/gdata /mnt/<gluster mount dir> >> >> >> Thanks, >> >> Eco >> On 11/20/2012 09:42 AM, Steve Postma wrote: >> >> >> I have a 3 node gluster cluster that had 3.1.4 uninstalled and 3.3.1 >> installed. >> >> I had some mounting issues yesterday, from a rocks 6.2 install to the >> cluster. I was able to overcome those issues and mount the export on my >> node. Thanks to all for your help. >> >> However, I can only view the portion of files that is directly stored on the >> one brick in the cluster. The other bricks do not seem to be replicating, >> tho gluster reports the volume as up. >> >> [root@mseas-data<mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data><mailto:root@mseas-data> >> ~]# gluster volume info >> Volume Name: gdata >> Type: Distribute >> Volume ID: eccc3a90-212d-4563-ae8d-10a77758738d >> Status: Started >> Number of Bricks: 3 >> Transport-type: tcp >> Bricks: >> Brick1: gluster-0-0:/mseas-data-0-0 >> Brick2: gluster-0-1:/mseas-data-0-1 >> Brick3: gluster-data:/data >> >> >> >> The brick we are attaching to has this in the fstab file. >> /dev/mapper/the_raid-lv_data /data xfs quota,noauto 1 0 >> >> >> but "mount -a" does not appear to do anything. >> I have to run "mount -t xfs /dev/mapper/the_raid-lv_data /data" >> manually to mount it. >> >> >> >> Any help with troubleshooting why we are only seeing data from 1 brick of 3 >> would be appreciated, >> Thanks, >> Steve Postma >> >> >> >> >> >> >> >> ________________________________ >> From: Steve Postma >> Sent: Monday, November 19, 2012 3:29 PM >> To: >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> Subject: cant mount gluster volume >> >> I am still unable to mount a new 3.3.1 glusterfs install. I have tried from >> one of the actual machines in the cluster to itself, as well as from various >> other clients. They all seem to be failing in the same part of the process. >> >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> >> >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> ________________________________ >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> >> >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> ________________________________ >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> >> >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> ________________________________ >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users >> >> >> ________________________________ >> _______________________________________________ >> Gluster-users mailing list >> [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> >> http://supercolony.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ > Gluster-users mailing list > [email protected]<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > http://supercolony.gluster.org/mailman/listinfo/gluster-users > ________________________________ > _______________________________________________ > Gluster-users mailing list > [email protected]<mailto:[email protected]><mailto:[email protected]> > http://supercolony.gluster.org/mailman/listinfo/gluster-users > ________________________________ > _______________________________________________ > Gluster-users mailing list > [email protected]<mailto:[email protected]> > http://supercolony.gluster.org/mailman/listinfo/gluster-users ________________________________ _______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
