From owner-freebsd-questions@freebsd.org Thu Sep 13 19:51:49 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 E0A4910979EA for ; Thu, 13 Sep 2018 19:51:49 +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 7DAA5801DF for ; Thu, 13 Sep 2018 19:51:49 +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 w8DJVd5w065112 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 13 Sep 2018 15:31:39 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Thu, 13 Sep 2018 15:31:39 -0400 (EDT) From: Daniel Feenberg To: freebsd-questions@freebsd.org Subject: Gnome and Firefox, lockd and NFS Message-ID: 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/13 14:02:00 #8529531 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: Thu, 13 Sep 2018 19:51:50 -0000 We are using the NFS server on FreeBSD 10.3-RELEASE-p7 to serve home directories to Linux SL7 (same as Centos7 and RH7) clients via NFSv3. While this worked fine with SL6, we find that starting Firefox, Gnome or Mate causes the client to hang with the message: nfs server XXX not responding, still trying and (for example) ~/.mozilla/firefox/XXX/.nfs00000000000XXXXXXXXX file stuck If one tries to remove the lock, the client responds: Cannot remove, Device or resource busy Furthermore, the server quickly stops serving *all* other clients also. If we kill the client process, then the server recovers after a few minutes. 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. 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. Daniel Feenberg National Bureau of Economic Research