From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Mike Kupfer Newsgroups: gmane.emacs.devel Subject: Re: Emacs Hangs on Filesystem Operations on Stale NFS Date: Mon, 11 Jun 2018 09:46:24 -0700 Message-ID: <7636.1528735584@alto> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: blaine.gmane.org 1528735588 14418 195.159.176.226 (11 Jun 2018 16:46:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 11 Jun 2018 16:46:28 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 11 18:46:23 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fSPxS-0003YM-Dp for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2018 18:46:18 +0200 Original-Received: from localhost ([::1]:50186 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSPzZ-00067o-7P for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2018 12:48:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44511) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSPxo-0005Qc-8p for emacs-devel@gnu.org; Mon, 11 Jun 2018 12:46:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fSPxj-0003BP-5z for emacs-devel@gnu.org; Mon, 11 Jun 2018 12:46:40 -0400 Original-Received: from shell1.rawbw.com ([198.144.192.42]:39736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSPxi-0003AZ-Sh for emacs-devel@gnu.org; Mon, 11 Jun 2018 12:46:35 -0400 Original-Received: from alto (96-95-200-133-static.hfc.comcastbusiness.net [96.95.200.133]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w5BGkOpe090982 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2018 09:46:31 -0700 (PDT) (envelope-from mkupfer@alum.berkeley.edu) X-Authentication-Warning: shell1.rawbw.com: Host 96-95-200-133-static.hfc.comcastbusiness.net [96.95.200.133] claimed to be alto In-Reply-To: Your message of "Mon, 11 Jun 2018 11:04:47 -0400." X-Mailer: MH-E 8.6+git; nmh 1.6; GNU Emacs 26.1 Content-ID: <7635.1528735584.1@alto> X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 198.144.192.42 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:226228 Archived-At: Stefan Monnier wrote: > - It seems your unreliable NFS server is mounted "hard" rather than "soft". > Why is that? "man mount" on my Debian machine doesn't find any "hard" > or "soft" options, so has the soft-mount option disappeared? Try nfs(5) for a description of "hard" and "soft". If you don't have that man page installed, it should be on the web somewhere. Hard mounts are the default because soft mounts usually cause more problems than they solve. > What are > applications usually expected to do when accessing a stale NFS server? Could we start by getting a more precise definition of "stale NFS server"? I can think of at least 3 different situations that might be meant: - the server is down temporarily - the server is down permanently - the server is up, but it no longer exports that filesystem And if the mount is managed by the automounter, the application behavior will depend on whether the mount has already been established. (I think. I'm very familiar with the Solaris NFS implementation, but not the Linux implementation.) mike