Return-Path: Received: from smtp-o-3.desy.de ([131.169.56.156]:51634 "EHLO smtp-o-3.desy.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753368AbdCTUv2 (ORCPT ); Mon, 20 Mar 2017 16:51:28 -0400 Received: from smtp-map-3.desy.de (smtp-map-3.desy.de [131.169.56.68]) by smtp-o-3.desy.de (DESY-O-3) with ESMTP id 2E3A62804E8 for ; Mon, 20 Mar 2017 21:51:24 +0100 (CET) Date: Mon, 20 Mar 2017 21:51:21 +0100 (CET) From: "Mkrtchyan, Tigran" To: Olga Kornievskaia Cc: Linux NFS Mailing list , Steve Dickson Message-ID: <362211751.3088036.1490043081358.JavaMail.zimbra@desy.de> In-Reply-To: References: <45574919.3034342.1490025160438.JavaMail.zimbra@desy.de> Subject: Re: pNFS: invalid IP:port selection when talks to DS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: Hi Olga, ----- Original Message ----- > From: "Olga Kornievskaia" > To: "Mkrtchyan, Tigran" > Cc: "Linux NFS Mailing list" , "Steve Dickson"= > Sent: Monday, March 20, 2017 9:14:34 PM > Subject: Re: pNFS: invalid IP:port selection when talks to DS > Hi Tigran, >=20 > While I don't have an answer to your question, I'd like to point out > that in 4.9 is when Andy's session trunking patches when in. >=20 > I'm curious this client that's now talking to the DS at port 24006 > instead of 24005, did it before also earlier correctly (legally) > talked to DS that was on 24006? Yes, earlier during testing it had legal access to DS on port 24006. Tigran. >=20 > On Mon, Mar 20, 2017 at 11:52 AM, Mkrtchyan, Tigran > wrote: >> >> >> Dear (p)NFS-ors, >> >> we observe VERY unpleasant situation with pNFS in the production. >> Our hosts run multiple DSes on different ports, usually 24001-24009. >> With CentOS7 (3.10.0-514.6.2.el7.x86_64) we see that client takes >> a wrong port number when talks to data server: >> >> If client uses different DSes on the same host, then at some point it st= arts >> to send data to the wrong port number: >> >> Client <=3D> MDS: >> >> >> 1 0.000000000 131.169.251.53 =E2=86=92 131.169.51.35 NFS V4 Call OPE= N DH: >> 0x7cbc716b/MIL-68-onebatch-80C-30s-00057.tif.metadata >> 2 0.001469799 131.169.51.35 =E2=86=92 131.169.251.53 NFS V4 Reply (C= all In 1) OPEN >> StateID: 0xec18 >> 3 0.001578128 131.169.251.53 =E2=86=92 131.169.51.35 NFS V4 Call SET= ATTR FH: 0x6ccf3dfa >> 4 0.002657187 131.169.51.35 =E2=86=92 131.169.251.53 NFS V4 Reply (C= all In 3) SETATTR >> 5 0.003243819 131.169.251.53 =E2=86=92 131.169.51.35 NFS V4 Call LAY= OUTGET >> 6 0.014603386 131.169.51.35 =E2=86=92 131.169.251.53 NFS V4 Reply (C= all In 5) LAYOUTGET >> 7 0.014899121 131.169.251.53 =E2=86=92 131.169.51.35 NFS V4 Call GET= DEVINFO >> 8 0.015014216 131.169.51.35 =E2=86=92 131.169.251.53 NFS V4 Reply (C= all In 7) GETDEVINFO >> Opcode: GETDEVINFO (47) >> Status: NFS4_OK (0) >> layout type: LAYOUT4_NFSV4_1_FILES (1) >> device index: 0 >> r_netid: tcp >> length: 3 >> contents: tcp >> fill bytes: opaque data >> r_addr: 131.169.51.50.93.197 >> length: 20 >> contents: 131.169.51.50.93.197 >> r_netid: tcp >> length: 3 >> contents: tcp >> fill bytes: opaque data >> r_addr: 131.169.51.50.93.197 >> length: 20 >> contents: 131.169.51.50.93.197 >> notification bitmap: 6 >> notification bitmap: 0 >> [Main Opcode: GETDEVINFO (47)] >> >> 9 0.105442455 131.169.251.53 =E2=86=92 131.169.51.35 NFS V4 Call TES= T_STATEID >> 10 0.105521354 131.169.51.35 =E2=86=92 131.169.251.53 NFS V4 Reply (C= all In 9) >> TEST_STATEID >> >> >> >> NOTICE, that 131.169.51.50.93.197 corresponds to port 24005. >> >> client <=3D> DS >> >> $ tshark -r ds-write.pcap -n -z conv,tcp >> 1 0.000000 131.169.251.53 =E2=86=92 131.169.51.50 NFS V4 Call WRIT= E StateID: 0xff01 >> Offset: 0 Len: 3968 >> 2 0.000090 131.169.51.50 =E2=86=92 131.169.251.53 NFS V4 Reply (Ca= ll In 1) WRITE >> Status: NFS4ERR_BAD_STATEID >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D >> TCP Conversations >> Filter: >> | <- = | | -> | | Total | Relative | Duration | >> | Frames Byt= es | | Frames Bytes | | Frames Bytes | Start | >> | | >> 131.169.51.50:24006 <-> 131.169.251.53:847 1 4= 240 >> 1 168 2 4408 0.000000000 0.0001 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D >> >> NOTICE, that it talks to DS on port 24006! >> >> Is there know fix which is missing in CentOS7? I can't reproduce it with >> 4.9 kernel (or it's harder to reproduce). >> >> >> The packages are attached. >> >> Tigran. >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html