From owner-freebsd-stable@freebsd.org Thu Dec 19 00:22:56 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 731B01CAAD0 for ; Thu, 19 Dec 2019 00:22:56 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47dXdr0Xd4z3wxv for ; Thu, 19 Dec 2019 00:22:56 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.nyi.freebsd.org (Postfix) id 126C21CAACF; Thu, 19 Dec 2019 00:22:56 +0000 (UTC) Delivered-To: stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 122A21CAACE for ; Thu, 19 Dec 2019 00:22:56 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670044.outbound.protection.outlook.com [40.107.67.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47dXdp1nJdz3wxt for ; Thu, 19 Dec 2019 00:22:53 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mMZdbdlqHPDIDoGpBrJRzjOtbIphzO4roTVOQMjJ98zNeun/9QuK/Sv4JM9FhaRI1sMoDdgo57lChAKec76132f1aGtDzFMTWEwwbdU/4t6mYx9HKIn+4p8cyjvH+cnFZrrTCqIJP66fLj+PfqPOjpZNM/5osOqplZrokqlktERjrIPMvJ9WBVtO3Ot7s5LEtywFxm1Tsz8X621Ee2t5uPv8fUeUi4WNi5c8XXGtWuIIPvoHJzZ5xMwxvd95LWZVyJonfDiRAgCKrLzklhmXKsinXI5qPDLqnVAwgUhIHUldWfyU0/bGyE++BprfDp7w3jkLdPZlLHMTE3AAwV3l1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3cSr3J7q4zdTHJlmr91dtI1CVJST62X4ZjuO8uH6xPE=; b=fr1MujSRVcg0XY56Bm4ubiGFBSNsCL1yMaFJ4gfA3IggHt3Pk3jArQiJlQR8qxc9+k/+DmABYJxTCLU0KQDyEtDFIK1V+iyJOyP9R9a8+o+jw6QPgAn8d/j5aeHrJOqYbdMKR8VxInJlNuw1iZvkx0vRAerP4gPmFv2f8NXtekYILdQTU85TsqLyk+xo9LUUYbXdDj+RUGD+yz1pwZ8JsYCdZoEMtg3Fn5AIuxxA8SB6IVPLmu/qElBpsB5/1K3UXa9ReFnImC2/DtPB5pFa2JhDdj+X8K37HBUFg6iam9lrjFZnqbg+8EYXEek4kqe/skFLLgFkpOxOug4ThqkkJg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uoguelph.ca; dmarc=pass action=none header.from=uoguelph.ca; dkim=pass header.d=uoguelph.ca; arc=none Received: from YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM (52.132.69.153) by YQBPR0101MB1332.CANPRD01.PROD.OUTLOOK.COM (52.132.68.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.16; Thu, 19 Dec 2019 00:22:52 +0000 Received: from YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM ([fe80::9504:a50d:ee12:b75]) by YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM ([fe80::9504:a50d:ee12:b75%5]) with mapi id 15.20.2538.019; Thu, 19 Dec 2019 00:22:52 +0000 From: Rick Macklem To: Richard P Mackerras , Daniel Braniss CC: "stable@freebsd.org" Subject: Re: nfs lockd errors after NetApp software upgrade. Thread-Topic: nfs lockd errors after NetApp software upgrade. Thread-Index: AQHVtawq+ga5QLcdVkqBDG/GW9zFg6e/+Am+gAARTACAAANHAIAAi7Y3 Date: Thu, 19 Dec 2019 00:22:52 +0000 Message-ID: References: <0121E289-D2AE-44BA-ADAC-4814CAEE676F@cs.huji.ac.il>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 672e2b26-d2c6-45db-8aff-08d7841995f1 x-ms-traffictypediagnostic: YQBPR0101MB1332: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 0256C18696 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(39860400002)(396003)(376002)(346002)(199004)(189003)(52536014)(26005)(66946007)(4326008)(53546011)(966005)(86362001)(2906002)(6506007)(316002)(478600001)(110136005)(786003)(71200400001)(186003)(33656002)(81166006)(7696005)(8936002)(81156014)(66446008)(64756008)(66556008)(66476007)(55016002)(9686003)(5660300002)(8676002)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:YQBPR0101MB1332; H:YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 2xzC5CR7NHJDgvR/iqpyjWe/FGZj9/WePKhqWpsVAX7VtFZsUUvQ8Fm2cxYHYADGSRfLxeoI3RCu7QkmOG8v4j56gqK6pJHphDBr35OdtM1MDYXC/Jg56N7pMvQM13BkL2sECglAXIJ5xIxLbHmVSM1SUd0oHyN7g09tM5IHPy8uCjJDl0CRxlUxOJamYDfAVw8KWuOivTynReP4bly2l9m1OJpHBdYvNNfWiyemXlophKRNuK0dUjcD7esv1zCEv86zqRKCsQLewMureefuFX7KCtSrlVTN3kJ1M/7Bd2uCUs1rCwUmY6D0RR4nQ9ZH56tF2K5WDlZc+P4qhGfp4jjWmEjxoO1x5q9taSnq5Hxbgvk6bWeYArPxtMWLEt37fuPlhxq3M9J0KKGv5O+jpUDkkjGG1QQPL500PeH44MIcWVdYQaevWdd3DfiD6ivaau9elxS2BCmyHrII0HuLKAhayPnsKHheP8rWGlZZSLo= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 672e2b26-d2c6-45db-8aff-08d7841995f1 X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2019 00:22:52.0288 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: JwzlVuNveRiyM++32qPL5MaHxJ4lMNMNSEuQ1NyO0ApVxUTkJg4cxx+1Q2fWUm6GF/wLNAzKxl57920Lhmglvw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: YQBPR0101MB1332 X-Rspamd-Queue-Id: 47dXdp1nJdz3wxt X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rmacklem@uoguelph.ca designates 40.107.67.44 as permitted sender) smtp.mailfrom=rmacklem@uoguelph.ca X-Spamd-Result: default: False [-4.66 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[uoguelph.ca]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[44.67.107.40.list.dnswl.org : 127.0.3.0]; IP_SCORE(-1.36)[ipnet: 40.64.0.0/10(-3.83), asn: 8075(-2.91), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8075, ipnet:40.64.0.0/10, country:US]; ARC_ALLOW(-1.00)[i=1] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2019 00:22:56 -0000 Richard P Mackerras wrote:=0A= =0A= >Hi,=0A= >What software version is the NetApp using?=0A= >Is the exported volume big?=0A= >Is the vserver configured for 64bit identifiers?=0A= >=0A= >If you enable NFS V4.0 or 4.1 other NFS clients using defaults might mount= NFSv4.x >unexpectedly after a reboot so you need to watch that.=0A= The FreeBSD client always uses NFSv3 mounts by default. To get NFSv4 you mu= st=0A= explicitly specify the "nfsv4" or "vers=3D4" mount option. For NFSv4.1, you= must=0A= also specify "minorversion=3D1".=0A= =0A= The Linux distros I am familiar with will use the highest NFS version suppo= rted by=0A= the server by default. (I suspect some are using NFSv4.1 without realizing = it,=0A= which isn't necessarily bad.)=0A= =0A= nfsstat -m=0A= will show you which version is actually in use for both FreeBSD and Linux.= =0A= =0A= rick=0A= =0A= Cheers=0A= =0A= Richard=0A= (NetApp admin)=0A= =0A= On Wed, 18 Dec 2019 at 15:46, Daniel Braniss > wrote:=0A= =0A= =0A= > On 18 Dec 2019, at 16:55, Rick Macklem > wrote:=0A= >=0A= > Daniel Braniss wrote:=0A= >=0A= >> Hi,=0A= >> The server with the problems is running FreeBSD 11.1 stable, it was work= ing fine for >several months,=0A= >> but after a software upgrade of our NetAPP server it=92s reporting many = lockd errors >and becomes catatonic,=0A= >> ...=0A= >> Dec 18 13:11:02 moo-09 kernel: nfs server fr-06:/web/www: lockd not resp= onding=0A= >> Dec 18 13:11:45 moo-09 last message repeated 7 times=0A= >> Dec 18 13:12:55 moo-09 last message repeated 8 times=0A= >> Dec 18 13:13:10 moo-09 kernel: nfs server fr-06:/web/www: lockd is alive= again=0A= >> Dec 18 13:13:10 moo-09 last message repeated 8 times=0A= >> Dec 18 13:13:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen= queue >overflow: 194 already in queue awaiting acceptance (1 occurrences)= =0A= >> Dec 18 13:14:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen= queue >overflow: 193 already in queue awaiting acceptance (3957 occurrence= s)=0A= >> Dec 18 13:15:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen= queue >overflow: 193 already in queue awaiting acceptance =85=0A= > Seems like their software upgrade didn't improve handling of NLM RPCs?=0A= > Appears to be handling RPCs slowly and/or intermittently. Note that no on= e=0A= > tests it with IPv6, so at least make sure you are still using IPv4 for th= e mounts and=0A= > try and make sure IP broadcast works between client and Netapp. I think t= he NLM=0A= > and NSM (rpc.statd) still use IP broadcast sometimes.=0A= >=0A= we are ipv4 - we have our own class c :-)=0A= > Maybe the network guys can suggest more w.r.t. why, but as I've stated be= fore,=0A= > the NLM is a fundamentally broken protocol which was never published by S= un,=0A= > so I suggest you avoid using it if at all possible.=0A= well, at the moment the ball is on NetAPP court, and switching to NFSv4 at = the moment is out of the question, it=92s=0A= a production server used by several thousand students.=0A= =0A= >=0A= > - If the locks don't need to be seen by other clients, you can just use t= he "nolockd"=0A= > mount option.=0A= > or=0A= > - If locks need to be seen by other clients, try NFSv4 mounts. Netapp fil= ers=0A= > should support NFSv4.1, which is a much better protocol that NFSv4.0.= =0A= >=0A= > Good luck with it, rick=0A= thanks=0A= danny=0A= =0A= > =85=0A= > any ideas?=0A= >=0A= > thanks,=0A= > danny=0A= >=0A= > _______________________________________________=0A= > freebsd-stable@freebsd.org mailing lis= t=0A= > https://lists.freebsd.org/mailman/listinfo/freebsd-stable=0A= > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org<= mailto:freebsd-stable-unsubscribe@freebsd.org>"=0A= =0A= _______________________________________________=0A= freebsd-stable@freebsd.org mailing list= =0A= https://lists.freebsd.org/mailman/listinfo/freebsd-stable=0A= To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"=0A=