Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752509AbbFSBIP (ORCPT ); Thu, 18 Jun 2015 21:08:15 -0400 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.226]:28032 "EHLO cdptpa-oedge-vip.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751467AbbFSBIH (ORCPT ); Thu, 18 Jun 2015 21:08:07 -0400 Date: Thu, 18 Jun 2015 21:08:43 -0400 From: Steven Rostedt To: Jeff Layton Cc: Trond Myklebust , Eric Dumazet , Anna Schumaker , Linux NFS Mailing List , Linux Network Devel Mailing List , LKML , Andrew Morton Subject: Re: [REGRESSION] NFS is creating a hidden port (left over from xs_bind() ) Message-ID: <20150618210843.4b09c31c@grimm.local.home> In-Reply-To: <20150618185051.2b2828c3@tlielax.poochiereds.net> References: <20150611234929.7b48d314@gandalf.local.home> <1434120035.27504.77.camel@edumazet-glaptop2.roam.corp.google.com> <20150612113420.5c114183@gandalf.local.home> <20150612115038.44e20ccd@gandalf.local.home> <20150617230819.0a11e47a@grimm.local.home> <20150618154914.57424225@gandalf.local.home> <20150618185051.2b2828c3@tlielax.poochiereds.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2784 Lines: 86 On Thu, 18 Jun 2015 18:50:51 -0400 Jeff Layton wrote: > The interesting bit here is that the sockets all seem to connect to port > 55201 on the remote host, if I'm reading these traces correctly. What's > listening on that port on the server? > > This might give some helpful info: > > $ rpcinfo -p # rpcinfo -p wife program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 34243 status 100024 1 tcp 34498 status # rpcinfo -p localhost program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 38332 status 100024 1 tcp 52684 status 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 2 tcp 2049 100227 3 tcp 2049 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100227 2 udp 2049 100227 3 udp 2049 100021 1 udp 53218 nlockmgr 100021 3 udp 53218 nlockmgr 100021 4 udp 53218 nlockmgr 100021 1 tcp 49825 nlockmgr 100021 3 tcp 49825 nlockmgr 100021 4 tcp 49825 nlockmgr 100005 1 udp 49166 mountd 100005 1 tcp 48797 mountd 100005 2 udp 47856 mountd 100005 2 tcp 53839 mountd 100005 3 udp 36090 mountd 100005 3 tcp 46390 mountd Note, the box has been rebooted since I posted my last trace. > > Also, what NFS version are you using to mount here? Your fstab entries > suggest that you're using the default version (for whatever distro this > is), but have you (e.g.) set up nfsmount.conf to default to v3 on this > box? > My box is Debian testing (recently updated). # dpkg -l nfs-* ii nfs-common 1:1.2.8-9 amd64 NFS support files common to clien ii nfs-kernel-ser 1:1.2.8-9 amd64 support for NFS kernel server same for both boxes. nfsmount.conf doesn't exist on either box. I'm assuming it is using nfs4. Anything else I can provide? -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/