From owner-freebsd-questions@freebsd.org Sat Sep 15 17:55:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ECCB10806DD for ; Sat, 15 Sep 2018 17:55:46 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mail2.nber.org (mail2.nber.org [198.71.6.79]) by mx1.freebsd.org (Postfix) with ESMTP id E10AC9327E; Sat, 15 Sep 2018 17:55:45 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from sas1.nber.org (sas1.nber.org [198.71.6.89]) by mail2.nber.org (8.15.2/8.15.2) with ESMTPS id w8FHtbjV041117 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 15 Sep 2018 13:55:38 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Sat, 15 Sep 2018 13:55:37 -0400 (EDT) From: Daniel Feenberg To: Rick Macklem cc: =?UTF-8?Q?T=C4=B3l_Coosemans?= , "rmacklem@FreeBSD.org" , "freebsd-questions@freebsd.org" Subject: Re: Gnome and Firefox, lockd and NFS In-Reply-To: Message-ID: References: , <20180915130133.70c66339@kalimero.tijl.coosemans.org> User-Agent: Alpine 2.21 (LRH 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Status: not scanned, disabled by settings X-KLMS-AntiSpam-Interceptor-Info: not scanned X-KLMS-AntiPhishing: Clean, 2018/09/11 07:55:10 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2018/09/15 13:48:00 #8550401 X-KLMS-AntiVirus-Status: Clean, skipped X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2018 17:55:46 -0000 On Sat, 15 Sep 2018, Rick Macklem wrote: > >> Our workaround has been to move the directories .local, .config and .dbus >> in the home directory to an NFS partition that is mounting without >> locking, but this seems inadequate as a permanent solution. >> >> Since the FreeBSD server stops responding to other clients, it seems it >> must be a FreeBSD problem. > I think you have a "livelock" type problem, where the client is flooding the > server with RPCs. > To check, you could capture packets when it happens and look at them with > wireshark, which understands NFS RPCs well. Can you refer me to posting with more detailed discussion of the "livelock" problem? A half hour with Google doesn't show anything relevant. Daniel Feenberg > >> Even if the Linux client (systemd?) is making >> an improper request, it is inappropriate for FreeBSD to hang in response. >> We also see this same result with Truenas and FreeNAS fileservers (which >> are based on FreeBSD) but see https://redmine.ixsystems.com/issues/927 for >> another report related to earlier clients. A Linux NFS server does not >> display this problem. > Part of the problem with the NLM is that no two implementations will be 100% > compatible, since there was never any published spec (like an RFC) for the > protocol. Each implementation tries various tricks to make it work better. > I suspect some change between the implementations in SL6 and SL7 triggered > this. (Since the protocol is unpublished and fundamentally flawed, I don't try > and fix it and just suggest the above when anyone has problems with it.) > > rick > >> >> Daniel Feenberg >> National Bureau of Economic Research > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >